← All articles
6 min readProcess,Product Development,Small Teams,Engineering Culture

A Disciplined Product Development Process

By Mykhailo Boichuk · Chief Technology Officer

In short

Process should answer the problem a team actually has. Most of the discipline in product development comes from three habits: limiting work in progress, writing down decisions so shared understanding does not depend on memory, and finishing one thing before starting the next. Ceremony added without a problem to solve slows delivery and protects nothing.

Process should fit the problem

Much published software process is built for organizations in which coordination across many groups is the central problem. A team that owns a product end to end faces a different constraint: the cost of unfinished work and of decisions nobody recorded. Ceremonies designed for another constraint add overhead and leave the real one untouched.

The useful question is which discipline a given team needs. The answer is usually narrower than it first appears. A few habits, applied consistently, do most of the work that elaborate process is meant to do.

Limit work in progress

The most valuable discipline in product development is limiting how much is underway at once. When several efforts run in parallel on the same people, each advances slowly and none reaches a finished state. Finishing one thing before starting the next keeps quality high and makes progress visible.

  • Keep the number of active efforts small, ideally one significant thing per person.
  • Finish and ship before opening new work.
  • Treat a long list of half-done features as a warning sign. It measures activity and says nothing about progress.

Write decisions down

It is tempting to keep decisions in conversation and memory. That works until it does not. Decisions get forgotten, the reasons behind them are lost, and the same questions get reargued. A brief written record is cheap insurance against all of this.

A record of what was decided and why does not need to be formal. A few sentences captured at the time keep shared understanding intact as the code and the people working on it change.

Protect focus and quality

Focus is the advantage these habits protect. Protecting it means saying no to scope that does not serve the core of the product, and refusing to let unfinished, low-quality work accumulate as debt.

At BBMM the process is deliberately light: agree on what to build and why, build one thing at a time to a finished standard, write down the decisions that matter, and ship. The discipline lies in applying these habits every time. A team that finishes what it starts and remembers why it made its choices delivers steadily, release after release.

Key takeaways

  • A few consistent habits carry a product team further than process built for a different problem.
  • Limiting work in progress keeps quality high and progress visible.
  • Finish and ship one thing before starting the next.
  • Writing decisions down briefly prevents the loss of shared understanding.
  • Protecting focus and refusing low-quality work keeps delivery steady.

Frequently asked questions

Does a product team need a formal development process?
It needs a few disciplined habits that match its real constraints. Coordination-heavy process helps where coordination is the main problem and adds overhead everywhere else.
What is the most important discipline in product development?
Limiting work in progress. Finishing one thing before starting the next keeps quality high and makes progress visible.
Why write decisions down?
Relying on memory leads to forgotten decisions and reargued questions. A brief written record preserves shared understanding at little cost.

About the author

Mykhailo Boichuk

Chief Technology Officer

Mykhailo builds the systems behind the apps. He works on macOS and iOS performance, and on the sync problems that come with software that has to run offline.