01
The task queue is formed randomly
The next task is whatever was requested most loudly. Business impact is not assessed, so inexpensive important changes wait for months.
Launch is not the finish. It is when the first real data appears.
We lead the product after release: we collect a backlog of changes for business impact, release them regularly and we verify result. We remove features that do not work instead of building new ones on top of them.
When this needed
A product grows through features, not the result
Development is needed when the product already works and changes are released constantly, but nobody can say which produced an effect.
02
Releases are unpredictable
There is no release rhythm: changes accumulate, ship in a large block and break what worked.
03
Results are not checked
A feature is released – and on this that is all. A year later, no one remembers why it exists or whether anyone uses it.
04
The product becomes more complex
interface overloaded, new new users cannot understand it, support becomes more expensive with each release.
Product development is not a race to ship features. This quality of decisions about what to do next.
Team work
What included in growth product
-
01
Business-impact backlog
Every task has a reason, expected effect, cost and risk. The execution order is visible and clear to the whole team.
-
02
research before development
Data product, support requests, user interviews. we verify hypothesis to that, as spending weeks on development.
-
03
Design and development changes
Journey, interface, implementation and testing in within existing architecture and design-systems product.
-
04
Regular releases
Predictable release rhythm, test environment, plan rollback. Smaller changes more often – lower risk and faster feedback.
-
05
Result verification
What changed in the metrics after release, or the hypothesis was confirmed, that we do next: we grow, simplify or remove.
-
06
Technical health
Planned updates, work with accumulated technical debt and performance – so that each next change not cost more in the future.
Boundaries: we do not take on product management without access to data and a responsible person on your side. Without this growth turns into execution random tasks.
Cycle
Every change passes full circle
- 01Data and requests
- 02Hypothesis and priority
- 03Design and development
- 04Release
- 05Verification and decisions
Not each hypothesis be confirmed – this normal part of the work. It is not normal not verify its at all and build subsequent decisions on assumptions.
-
01
meeting 30 minutes
What for product, who uses it, which goals on next months and that now in progress.
-
02
Backlog deep dive and audit
Data product, current challenges, state code. We rebuild the backlog by impact and we show, that worth remove.
-
03
first cycle changes
several small releases with measurable impact. Yes is checked and product, and our shared work.
-
04
Continuous rhythm
Monthly planning, releases, review of results and priority updates together with your team.
Cost
We charge for team and work rhythm, and not number features
Hosting, licences and external services are paid separately to their providers.
Audit product and backlogOne-off
from $2 500
state product, rebuilt backlog changes and plan on next months. Document remains in you.
- Analysis data and enquiries
- Assessment current backlog
- Backlog by impact
- Risks and technical debt
Continuous growthMonthly
from $4 000 / month.
Team for challenges month, regular releases and review of results.
- Planning and priorities
- Design and development changes
- Releases with testing
- Monthly metrics review
Questions
What usually ask about growth product
Support retains system in working condition: monitoring, updates, incidents. development changes the product: new scenarios, features and improvementss, which affect on money. They often run in parallel, but this different budgets and different success criteria.
No. We plan sprint or month for current priorities and rebuild the backlog for results. Annual plan features usually becomes outdated earlier, than can be delivered.
The decision is yours. We prepare backlog with impact estimate, cost and risk and explain the order. If you choose a different priority – we fix this and we work with it.
We suggest remove or simplify. Every unnecessary feature costs money in maintenance and complicates interface for remaining users.
We assemble the team for challenges month: product, design, development, analytics. The core part – and, that retains project context, rest joins as needed.
Code, access, documentation, backlog and history decisions. Product has continue to evolve without us – this condition, and not bonus.
Start
Let us look at your backlog – and on that, that with it truly worth developing
30 minutes online with founder. We will review the product, current challenges and goals, we will say, with what start cycle. Summary we will send in writing.