Small products. Real needs.
An idea does not have to become a platform. A useful beginning can be as small as making one person's everyday task easier.
Start with a moment, not a feature list
New product ideas often arrive as lists: take notes, send reminders, compare options, share results. As the list grows, the idea can feel more complete. Yet its length says very little about how clearly we understand the need. A specific moment of use offers a more useful starting point.
Where does someone pause during their day? Which task do they repeat in the same way? What information do they move between two places? The answer can be small and still worth attention. A product built around a particular moment can explain what it improves. “Capture a thought before losing it” gives a first version clearer boundaries than “Organise everything”.
Small can still feel complete
Keeping a product's scope small is an opportunity to give its details more care. A tool that does only a few things should consider each of them from beginning to end. Opening the product, starting the first task, receiving feedback and recovering from an error all belong to the same experience. Even a single calculation needs thoughtful inputs and a readable result.
A narrow scope makes room for this work. One considered flow can offer more value than ten unfinished ones. A complete first version does not have to account for every possible future. It has to keep the promise it makes now. That promise can be modest, specific and meaningful.
A first version earns its place by meeting a need.
Make the assumptions visible
Working on an idea means separating what we know from what we are guessing. “This task is difficult” might be an observation. “People will use this every day” is an assumption that needs exploring. Treating both with the same certainty can make a small product grow before it has found its purpose.
A rough sketch, one working screen or a partly manual flow can make an assumption easier to discuss. The useful signal is when someone needs the product, how it fits their habits and where they hesitate. Before asking whether they would use a new idea, it helps to understand how they handle the task today. Their existing behaviour gives the conversation something concrete to work with.
Boundaries help things move
Defining scope involves choosing what to make and being clear about what can wait. A first version of a note tool may leave shared editing for later. A calculator may focus on one type of calculation. These decisions keep the product's promise understandable and make it possible to give that promise proper attention.
“Would this be nice?” is usually too generous a question when considering a feature. “Will it make the main task easier?” is more useful. Every option brings another behaviour to learn, maintain and support. Sometimes a good idea is best saved for another moment. A boundary gives progress a direction.
Let the first useful thing lead
Starting small leaves the future open. When a first version meets a need clearly, later decisions have firmer ground. A recurring obstacle can be improved. A new need that emerges naturally can suggest the next addition. The product can grow through what it learns in use, at a rhythm that makes sense for the people using it.
That is how we approach making at Litken: notice a need, shape a focused idea and give the experience care. Then try it, listen and revisit the decisions. A product's value is easier to understand through the task it makes simpler than through the number of screens it contains. One useful thing is a good place to begin.