At Remote, we simplify processes—or eliminate them altogether—whenever possible. This guide provides detailed information and guidance on organizing work, along with best practices for achieving success.
Table of contents:
Our principles serve as the foundation for everything we do.
Bias Toward Action
Be proactive to keep the team productive and shipping
Small, iterative changes
We move more quickly and reduce risk
Minimal ≠ Bad
“Nothing lasts, nothing is finished, and nothing is perfect.” - Wabi Sabi
When shipping a Minimum Viable Product (MVP):
remember that MVP does not mean ship something that's half-baked and/or bad
Minimal: Characterized by simplicity and lack of adornment or decoration
Viable: Capable of working successfully; feasible
Loveable: Capable of working successfully; feasible, while delighting the user
Product: A thing that is the result of an action or process
No Blanket approach OR one size fits all
We won’t find a blanket approach/one size fits all - rather, look at it case by case basis (0-1 product vs mature scaled product etc)
💡 Pro Tip: Stay nimble and open-minded rather than dogmatic when solving problems.
Formalizing our product development lifecycle ensures a consistent, efficient, and collaborative approach as our team scales.
This benefits our company in several ways:
✋🏼 Note: The teams listed are examples and may vary depending on the stage - listed in an effort to illustrate the involvement of other teams throughout the development lifecycle stages.
Stages of the Product Development Lifecycle at Remote