01 / PLANNING
Write a brief that starts a useful conversation.
Begin with the people who will use your product. Describe what they are trying to do, what makes it difficult today, and how you would know the experience had improved.
List the essential journeys: for example, finding a service, requesting a quote, or tracking an order. Separate what must work on day one from ideas that could wait.
Include your existing content, systems, constraints, and the person who can make decisions. A rough brief with clear questions is a better starting point than a long feature list with no priorities.
Talk through your brief ↗02 / PRODUCT THINKING
Give your first version one clear job.
Choose one meaningful outcome for the first release. For a booking tool, that might be helping someone find a suitable time and receive confirmation.
Walk through that journey from beginning to end. Include the less obvious moments: no available slots, a missing field, or a connection that fails. Those details are part of the experience.
Review the working version with the people who will use it. Let their difficulties guide the next iteration, and keep a separate list of ideas for later.
Explore app development ↗03 / LEARNING
Turn a small project into a learning habit.
Choose something small enough to finish: a reading list, a portfolio, or a simple expense tracker. Write down the main task before choosing features.
Build one working piece, test it, and record what you learned. When you get stuck, reduce the problem to a smaller example and explain what you expected to happen.
Keep a README that explains how to run the project, the decisions you made, and what you would improve next. A finished, understandable project gives you something concrete to discuss with a mentor.
Explore learning paths ↗