Back to Resources

App Philosophy · 2 of 5

Roles with Clear Outcomes: The Thinking Behind Performance

A title is a label. A role is a designed set of outcomes with a purpose, a set of responsibilities, and a metric — and the metric should be born where the role is designed.

ProfitShapersPublished June 26, 20265 min read

The ecosystem is a family of purpose-built apps, each doing one job well — the philosophy behind the platform. Performance's one job is the layer most org tools skip entirely: not who reports to whom, but what each role is actually for. That distinction is the whole reason the app exists.

Boxes and lines aren't enough

An org chart is necessary but shallow. It captures reporting structure — boxes and lines — and stops there. It says nothing about what each role is responsible for, how its contribution is measured, or whether the org is over- or under-staffed for the work it's trying to do. Most org-design tools never go past the boxes. Performance adds the layer on top: deliberate role design, where every role has a defined purpose, defined responsibilities, and defined KPIs.

KPIs born where the roles are designed

There's a second conviction baked into the app: KPI definitions belong where the roles are designed, not invented separately downstream. Because a KPI is how a role's contribution is measured, authoring the definition next to the role means the metric flows from "what is this role for" rather than being dreamed up in a generic tool with no connection to a real job. The KPI Dashboard inside Performance scores those definitions weekly — keeping the numbers anchored to roles that actually exist.

What Performance is — and isn't

It's a role-design and capacity-diagnostics tool that authors KPI definitions, not scores. It is not an HRIS, an applicant tracking system, or a workforce-planning tool — hiring and payroll are out of scope — and AI doesn't design the roles or the KPIs for you.

Designing roles deliberately is how Leadership & Role Capacity gets built — value that lives in the design of the organization rather than in a few indispensable heads. And because capacity diagnostics like overload and underload flags surface upward, the role design feeds Execution Evidence & Value Movement too. The full product detail is on the Performance page; this essay is the thinking behind it.

Design the roles, not just the boxes

Start a 30-day free trial and give every role a purpose, a responsibility, and a metric.

Where should you start?

Take the two-minute Starting Point Quiz and we'll point you to the right app for your situation.

Get the next field note

One considered email when we publish something worth your time. No noise.