The Business section houses all product-related documentation that defines, guides, and oversees delivery. Its’ purpose is simple: create a transparent, versioned space where product owners make informed decisions, while design and development integrate seamlessly through automation.
This section typically includes core and aspirational values, product strategy, delivery roadmaps, and rollout plans. It also contains editable product definitions, OKRs, ROI models, budget overviews, risk assessments, and legal or compliance considerations - in a format that is easy to maintain and share. When structured well, this space enables product owners to justify feasibility and defend decisions with clarity.
As one product owner once put it: “Transparency makes the team more involved in cost-saving activities — how best we can achieve X.”
To illustrate this impact, let me share a short example.
An Italian Product Owner joined a large programme managing 27 independent features. Two months later, when I joined the team, instead of receiving a folder of Word and Excel files - as is common - I received a single Confluence link. The material was highly business-oriented, yet it immediately revealed an opportunity for shared ownership between product and design.
Within weeks, we reorganised the 27 features into five coherent propositions - creating the core offering for the UK’s largest broadcaster. Because all material lived in editable text, we simplified the hierarchy and reduced nearly three million words of scattered documentation into a clear, navigable structure. This unified strategy aligned OKRs, KPIs, and the rolling roadmap. Design stopped “colouring in” and became responsible for defining behaviour alongside the CPO® and BA colleagues.
The impact was significant:
— Transparency increased across product leadership.
— Designers gained clarity on business and customer objectives.
— Engineers stopped searching for fragmented briefs and instead built from verified BDD user stories.
— Reporting time across three major programmes dropped by 32%.
— Overall business impact rose by 62%.
The essential enabler of all this? A basic working knowledge of Atlassian tools — and a shared commitment to use them well.
