Ship your MVP to real users and learn from their behaviour
This week puts the MVP in front of real users. You will plan onboarding, observe behaviour, collect structured feedback, and decide what to fix first.
A beta is a learning period with a clear question. Decide what successful use looks like, which users qualify, what you will measure, and what support you can provide. Tell users the product is early and explain how to report problems.
Track a small number of events: arrival, account creation, first meaningful action, completion, and return. Analytics show what happened. Interviews and recordings help explain why. Avoid collecting more personal data than the test requires.
During a usability session, give the user a realistic task and let them work. Ask them to think aloud. Do not teach the interface while testing it. Confusion is useful evidence.
Group feedback into bugs, usability problems, missing value, and requests. Rank items by user impact, frequency, confidence, and effort. Fix broken core flows before adding attractive extras.
Approximately 113,000 views
Why it fits: A recent explanation of finding early believers, learning from churn and letting early users shape the product.
Recruit five suitable beta users personally and track what each person tries, completes and abandons.
The video supports the lesson above — it doesn't replace it.
Organise this beta feedback into bugs, usability issues, missing value, and feature requests. Merge duplicates but preserve the original evidence. Score each item for impact, frequency, confidence, and effort. Recommend the next five actions and explain why each one matters to the core workflow.
Week 8 · Case study
Source note: Documented founder story published by Lovable. User growth and timing are reported figures; the safety warning is course guidance. The student-sized version below is an illustrative exercise, not part of the reported case.
In 2025, Brazilian growth marketer Sabrine Matos used Lovable to create Plinq, a women’s safety platform providing access to public background information. The MVP was built in approximately 45 days.
Instead of waiting for a perfect product, the team released an early version and refined it using feedback from beta users. Lovable reports that Plinq reached more than 10,000 users during its first three months.
Because Plinq deals with safety and personal information, students should study its discovery and iteration process—not attempt to reproduce its sensitive data features without professional legal and security support.
Recruit five to ten beta users for a low-risk product. Give them a realistic task, observe without coaching, and record where they stop, hesitate, or misunderstand the interface.
Which finding would justify changing the core workflow rather than adding another feature?
Respond in your submission →Onboard ten beta users and submit a structured feedback report. Include the beta question, user criteria, onboarding flow, behaviour metrics, interview findings, prioritised fixes, and the changes you made.