Standard architecture: Consumer apps

How information is recorded, decided on and fed back. Mostly data and decisions, with information fed back.

Standard architectureThe parts at least half of the organizations in Consumer apps have, as many as 5 of them run all together. Counted from public, sourced parts only; each organization below links to the parts it was counted on.

Create a free account to save Create a free account to follow

Organizations running it: 5
Of their industry: 100%

The pattern

What every instance has, in order

Decisions
Market and positioning
in 100% of instances
money
Decisions
Pricing
in 100% of instances
then
Process
Product or service design
in 100% of instances
then
People
Org structure
in 100% of instances
then
Decisions
Governance and decision rights
in 100% of instances

Coloured arrows: a flow of that type seen between the two at instance organizations. Grey arrows: order only.

Structure

Groups Layers Everything

Element

Share of instances

Companies

Suppliers and partners

60%

Sales

20%

Variant · where they differ

Member

Variants, couplings and instances

Every level, number, source and dimension: Member, $300 a year.

See Member

Couplings · what comes together

Member

Variants, couplings and instances

Every level, number, source and dimension: Member, $300 a year.

See Member

Entropy

Where it runs rough

Operating-reality findings at instance companies: workarounds, manual hand-offs, bottlenecks.

Suppliers and partners1 finding
Dependency (public record) 1 · at 1 company

Seen across

Where it holds

Industries

Consumer apps100%

Business model

subscription100%

Size

1000+ people20%
201-500 people20%

Region

United States80%
Australia20%

Instances

The 5 companies it was seen at

Member

Variants, couplings and instances

Every level, number, source and dimension: Member, $300 a year.

See Member