<aside> 💡 Note, this handbook is public. Do not add any personal or confidential information to it.

</aside>

At Remote, we simplify processes (or get rid of them entirely) as much as possible. On this page, you'll find a little more detail and guidance on organising work, with some key best practices you should strive to follow.

Principles

  1. Bias Toward Action

    Be proactive to keep the team productive and shipping

  2. Small, iterative changes

    We move more quickly and reduce risk

  3. Minimal ≠ Bad

    “Nothing lasts, nothing is finished, and nothing is perfect.” - Wabi Sabi

    When shipping an MVP (minimum viable product), 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

    Product: A thing or person that is the result of an action or process

  4. Quality over Quantity

    It is better to do one thing very well as opposed to multiple things poorly; minimise output and maximise impact and outcomes

Our Product Development Lifecycle & Processes

Formalising our Product Development Lifecycle is crucial for maintaining a unified approach to working as our team grows.

This benefits our company in several ways:

  1. By implementing distinct checkpoints for review, feedback collection, and clearly assigning owners for specific action items, we make cross-team collaboration more streamlined and efficient

  2. The structured approach to each stage of product development allows us to identify and mitigate risks earlier on, protecting our customers and ensuring compliance with industry regulations

  3. A centralised location for all important information about initiatives allows us to effectively track progress and measure success on a regular basis

  4. This facilitates knowledge sharing and training about product processes for new team members and non-product stakeholders

Stages of the Product Development Lifecycle 🔄

✋🏼 Note: The ****Teams Involved listed **may not be exhaustive for any given stage but listed in an effort to illustrate the involvement of other teams throughout the development lifecycle stages

Stages of the Product Development Lifecycle at Remote

Stages of the Product Development Lifecycle at Remote

Rationale 🗒️

The purpose of the Rationale phase is to quickly dismiss or decide to move forward with an initiative, before spending significant effort on it. Our hypotheses, proposed solution and minimal research will be validated and refined in the Discovery phase, should we choose to proceed.

🫂 Teams Involved: Product Manager (PM), Design, *Consulted* & Informed Stakeholders

📤 Deliverables: