App family

Strategy and delivery

Strategy made trackable, and the delivery work that serves it. Plans cascade to objectives with measures and readings; projects carry sponsors, budgets and milestones; products have releases; delivery runs in epics, work items and sprints — all pointing at the same outcomes, owned by the same people.

Who it's for

Written for the people who carry this

The executive team

The strategy is a document. Objectives have no owners, measures have no readings, and the quarterly review reconstructs progress from memory.

The PMO

Projects are reported in a deck assembled from six trackers. The sponsor, the budget and the milestones are in three places that disagree.

The product and delivery leads

Epics aim at nothing in particular. Work is tracked in a tool that has never heard of the product release or the objective it was meant to serve.

The apps

4 apps, one model underneath

Strategic planning

Strategy made trackable: plans, the objectives that cascade from them, the measures that say whether an objective is being met, and the readings taken against those measures. Use it so a strategy document turns into something with owners, numbers and a review rhythm.

Strategy plans · objectives · measures · measure readings

Project management

Projects and their tasks: who sponsors each project, what it is expected to cost, the milestones it has committed to, and how delivery is tracking. Use it for the reporting layer of project work rather than as a scheduling tool.

Projects · tasks

Product planning

Products and their releases: what you are building, who owns it, and what is planned to ship when. It gives delivery work a destination — an epic aimed at a release rather than at nothing in particular.

Products · releases

Delivery

Agile delivery: epics, work items and sprints. Epics carry the outcome being pursued, work items the individual pieces with their acceptance criteria, and sprints the timeboxes they are done in.

Epics · work items · sprints

How it connects. Strategic objectives can reference the risks that threaten them (governance). Project milestones and recurring reviews raise tasks through the platform.

Why one model

An objective, a project, an epic and a sprint agree on what they are for.

A strategic objective on Zubl is a record with an owner and a measure. Projects and epics point at it. Releases give delivery a destination. The same organisation tree scopes what each division sees of the plan, and the same people list names every sponsor and owner — so the roll-up to the executive view is a question, not a deck.

Not quite your shape?

Extend these apps, or build the one you need.

Every app here is open to extension on the same licence: a field, a lifecycle state, a link to a record in another family, a rule. Additions sit beside our definition and survive every upgrade.

And if the register your organisation needs is not here, describe it to the AI builder. It arrives governed — same access engine, same audit trail, same reports — because those belong to the platform, not to the app.

Extending and building →

We're working with design partners now.

A small number of organisations shaping the first release, in exchange for early access, direct influence over what ships next, and pricing that reflects the risk of going first.