Help for owners
Nobody decides what my developers should build, so they guess
Short answer
Someone on your side has to decide what is built next, answer the team's questions the same day, and say when a piece is accepted. That role is called a product owner. In a small business it is usually the owner or one trusted manager, given a short list and a fixed weekly slot.
Does this sound like your situation?
- Developers ask who decides, and different people in my company give different answers.
- Questions to the business sit unanswered for days and work stops or goes ahead on a guess.
- Sales, support and management each ask for their own features.
- Finished work is rejected because someone senior only saw it afterwards.
- Nobody on my side can say whether the work is going well.
Why does this happen?
The role was never given to anyone
In small companies the founder is the product owner by default but is busy with everything else. The role then exists on paper and nobody does it.
Several people each hold part of the decision
When sales, operations and management can each ask the developers directly, the developers must choose between them, which is not their job.
Answers are slow
Questions that wait for a week force a choice: stop working, or guess and risk redoing it. Both are costly.
Nobody accepts the work
If no single person says this piece is done and correct, defects and disagreements appear after release instead of before.
What can I do about it today?
- Name one personChoose who decides what gets built and in what order. It can be you. Tell the whole company and the developers the name.
- Set a response promise inside your companyAgree that the developers' questions are answered within a working day or two. This costs you little and saves them a lot.
- Collect requests in one placeA shared list or spreadsheet that only the named person reorders. Staff add ideas to it, not to the developers' inbox.
- Hold a short regular meetingThirty minutes weekly to look at what was built, answer questions and confirm the next items.
- Say when something is acceptedFor each finished piece, the named person writes a plain yes or a list of changes.
When should I bring someone in?
- The owner has no time and nobody else in the business can take on the role.
- The team makes product decisions because nobody else will, and you cannot judge them.
- You are choosing between building features and fixing problems and cannot weigh the trade-off.
How do I handle it?
- Find where decisions are made todayI trace who actually decides things now, and where requests and questions go.
- Prepare decisions for youQuestions reach you written plainly with the options, what each means and my recommendation, so a decision takes minutes.
- Keep one ordered listA single list of what is next, reordered only by the person you name.
- Hold the acceptance stepEach finished piece comes with a way to check it, so accepting it is quick and clear.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Does a small business need a full-time product owner?
Not usually. The role is a set of decisions, not a job title. One person with a few hours a week and clear authority can fill it.
Can the developer be the product owner?
They can advise, but the business should own the decisions about what matters to it. The developer can prepare options and explain the effects.
What if two senior people disagree?
Agree beforehand who has the final say. The developers should hear one decision.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.