Designing features, defining an architecture, creating a brand, or preparing a pitch… Developing a digital product, even in a small-scale environment such as a side project, requires a holistic vision that brings together multiple disciplines.
In the latest edition of SII Tech Talks, our colleague Aleix Riba, Tech Lead at SII Group Spain, shared an experience that goes far beyond a personal anecdote: a practical guide to building a digital product from scratch, covering every key stage of the process. Rather than focusing on the project itself, the session highlighted the journey, the decisions, the lessons learned, and the technical and strategic challenges that any team may encounter when developing a digital solution.
This article captures and summarizes that approach, which serves as a practical framework for both personal and professional innovation projects.
1. Think Like a Product: Prioritize, Simplify, Focus
The first step in any digital development project is not writing code, but defining the problem you are solving. Which features make sense? How should they be prioritized? What should the roadmap look like?
A product mindset means making decisions that have a real impact: deciding what to build first, what to postpone, and how to validate whether you are moving in the right direction. This is where key concepts such as the value proposition, the definition of an MVP (Minimum Viable Product), and alignment with real user needs come into play.
2. Purpose-Driven Design: UX/UI in Service of Functionality
Once the features are clearly defined, the next step is to bring them to life. Design goes far beyond aesthetics—it is a tool for communication and usability.
Through wireframes and prototypes, it is possible to visualize the user experience before implementation begins. The key is to combine visual fluidity with functional efficiency, ensuring that the product is not only attractive but also intuitive and easy to use from the very first click.
3. Development: Architecture, Quality, and Scalability
With a solid conceptual foundation in place, it is time to begin development. This stage involves challenges such as:
Choosing the right architecture to ensure scalability and maintainability.
Writing maintainable, well-tested code, avoiding the temptation of “if it works, it’s good enough.”
Optimizing performance, especially as the product grows.
This stage requires technical expertise as well as pragmatism: the goal is not to use the newest technology, but the one that best fits the context.
4. Visibility and Marketing: Telling the Story Behind the Product
Although it is often overlooked, knowing how to communicate what you have built is a fundamental part of a product’s lifecycle. It is not about running complex marketing campaigns, but about understanding how to position the product: How do we explain it in a demo? What tone should we use? Which channels are worth exploring?
Being able to tell the technical and functional story behind a product can make the difference between adoption and being forgotten.
5. Business Viability: Thinking About Sustainability
Although not every product is intended to become a commercial venture, evaluating its viability is always a valuable exercise. Is it sustainable over time? What would the maintenance costs be? Does it generate any kind of return?
Incorporating this perspective helps build a complete product mindset, even in purely technical environments.
6. Strategy: Making Decisions and Knowing When to Pivot
Finally, every product development journey needs a compass: a clear vision, defined objectives, and a sound strategy. This means knowing when to pivot, identifying mistakes early, and making course corrections based on continuous learning.
This is where principles such as the Lean model (build, measure, learn) and continuous validation become essential. Developing without a strategy means building blindly.
