Learning center
G01 · How to grow an online business systematically
G02 · Growth economics and the one-page commercial scorecard
G03 · Find the growth constraint and build a 90-day roadmap
G04 · Know your market, customer and value proposition
G05 · Acquire profitable customers and build demand
G06 · Map and improve the customer buying journey
G07 · Design a profitable product portfolio and pricing system
G08 · Prevent stock, delivery and fulfillment from blocking growth
G09 · Make customer relationships and retention profitable
G10 · Grow without destroying margin or cash flow
G11 · Build data and technology you can trust
G12 · Experiment, implement and learn safely
Operating cadence and continuous learning
Outcome: create a manageable decision rhythm for a small e-commerce team. A Growth System is not a meeting calendar. It is an arrangement in which evidence reaches the people authorized to choose, actions are owned, and outcomes are revisited.
Choose a cadence appropriate to the business. A small store may need a weekly growth review, quick operational exceptions during the week and a monthly economic review. A high-volume operation may require more frequent checks. Meeting frequency without purpose only creates administrative cost.
Design the weekly decision meeting
Distribute a short pre-read containing the objective, verified changes, blocked evidence, material exceptions and proposed decisions. In the meeting, spend time on choices that require cross-functional judgment. Avoid a tour of every dashboard. A useful agenda asks which constraint matters most, what evidence could reverse the current view, which initiative deserves capacity and whether existing work should stop.
Every commitment receives an owner and revisit rule. Uncertain items go into a validation queue, not the same queue as approved execution. Track capacity and dependencies so that a large backlog is not mistaken for a plan.
Monthly learning and economics
At a slower cadence, reconcile the commercial scorecard, contribution and cash requirements. Review released initiatives against baseline expectations, guardrails and data limitations. Look for repeated failures in measurement, QA, handoffs or decision ownership. Correct the operating mechanism rather than adding another one-off repair.
Worked example: experiments without learning
Imagine a team launches a sequence of product-page tests, but experiment briefs and final decisions are scattered across chat threads. Several ideas recur because nobody can find the earlier results. Introducing a single opportunity record and a monthly learning review may create more value than launching a fourth experiment that month.
Your first operating charter
Choose a recurring decision meeting with one named facilitator
Define a one-page pre-read and decision agenda
Maintain one prioritized backlog with approved, blocked and completed states
Set a review date and outcome standard for every released change
Use a monthly retrospective to change the process, not merely the tactics
Self-check: can someone new to the team find the current goal, approved initiatives, evidence quality, owner and last outcome without calling the consultant? If yes, your Growth System has started to become an institutional capability.
Explore the reference
01 · The four-step Growth System
02 · Nine connected growth levers
