<aside> 💡

This documentation is meant to be a brief summary of the key components of the Unit and the input we want to make to help us survive and cross the chasm.

</aside>

Product

⇒ This workstream is currently an effort being led by Patrick.

We have so little time to find product market fit for Meetwith, with that little time in mind and a sense urgency, we need to figure out how to get at least 20 paying customers for a version of Meetwith that we develop before the year runs out.

• We need to move super fast in delivering a valuable version of our product. We know this “valuable version of our product” by actively talking to users.
  • we should be able to know a valuable version of our product that users would love to make a part of their work after the first 20 interviews.
  • develop a product strategy document including detailed summary and insights from interviews, refined value proposition, detailed feature sets, ux requirements, design and development plan.
  • we need to identify all the feature sets and best design outcome for these feature sets. Deploying the process in our Product roadmap: Idea/Insight → inactive research → ready to be worked on → Prototype → In review → Validating → Design → Development → QA → Ready to announce → Done can be found Product Roadmap - Meetwith
  • when we check out (work on all of them as identified) all the important feature sets, the next focus will be fixing any arising issues as they come up and then intensify sales, marketing, community engagements.
• provide weekly/bi-weekly updates about the work going on in the team.

Engineering

⇒ This workstream is currently an effort being co-led by Ramon and Udoka.

How do this work contribute to finding PMF for Meetwith? Make the product reliable!

This team typically works with design and product:

• they own the product engineering work at Meetwith.
• they implement issues tickets in the product roadmap that has passed through inactive research → ready to be worked on → Prototype → In review → Validating → Design . this flow of feature development, improvement, bug fixing is not fixed. items that doesn’t need design can move research/idea to development.
• their implementations are meant to go through a quick QA and prepared for announcement.
• they can jump on any tiny issue that was reported which wouldn’t need much planning (when they are not working on anything) or have some free time after working on an agreed priority.

Design/Research

⇒ This workstream is currently an effort being led by Patrick.

How do this work contribute to finding PMF for Meetwith?

• design and deliver the brand materials.
• design the ui/ux of the feature sets identified by the product work and make it ready for development after user testing.

Brand/Marketing/Sales