Common situations
S4

Grown from 20 to 200, still run like 20

Your company has grown from 20 to 200 people in a short time, but it still operates much as it did when everyone knew each other. Now an important decision needs to be made and several people believe they have authority to approve it, while others are not sure who is actually responsible.

Show what is needed at

The minimal version a partner might accept.

2 standards bear on this

2

Organisational structure & roles

Helps you clarify key responsibilities, reporting lines and overlaps as the organisation grows.

Read 2 in full, with the challenges it runs into
2.1

Role definition for key functions

Getting started
  • List the key functions needed to run the company and support external cooperation
  • Identify who is responsible for each key function in practice
  • Cover at minimum finance, procurement, contracting, operations/production, security, HR/people, compliance/legal where applicable, and export or partner coordination
2.2

Functional structure and reporting lines

Getting started
  • Prepare a simple internal structure showing key functions and reporting lines
  • Use functions rather than personal names where this is safer or more practical
  • Include at least management, finance, procurement, operations/production, legal/compliance where applicable, security and export or partner interface roles
2.3

Role documentation and accessibility

Getting started
  • Record key responsibilities in an accessible form, such as job descriptions, role notes, process descriptions or employment contracts
  • Avoid relying only on chats, verbal instructions or individual memory
2.4

Partner-facing role explanation

Getting started
  • Identify which organisational information may be shared with external partners and who approves its disclosure
  • Avoid ad hoc sharing of internal charts, names or reporting lines
2.5

Governance and review

Getting started
  • Assign one person or function to maintain the organisational structure and role information
  • Define who approves changes to key roles, reporting lines and organisational responsibilities
3

Decision-making & authorities

Helps you clarify who can make, approve and escalate important decisions as responsibilities become more distributed.

Read 3 in full, with the challenges it runs into
3.1

Key decision categories

Getting started
  • Identify the main types of decisions that should not be left fully informal
  • Cover at least contracts, significant payments, procurement, supplier or intermediary engagement, export-related activity, sensitive hiring, partnerships, use of donations or support, and exceptions from standard practice
3.2

Decision authority and approval

Getting started
  • Define who initiates, reviews and approves/blocks each key decision category
  • Use existing tools where possible, such as email, task trackers and avoid relying solely on informal discussions for approvals of key decisions.
3.3

Escalation and high-sensitivity decision

Getting started
  • Identify decisions and situations that require enhanced review or escalation before a decision is final because they involve elevated legal, integrity, operational or security risks.
  • At a minimum, include decisions involving defence products, public-sector counterparts, export activity, intermediaries, complex or unusual payments, unclear ownership, sanctions or adverse media concerns, conflicts of interest, controlled technology, sensitive customers or end users, restricted information, urgent exceptions, or commitments outside normal authority.
  • Highly sensitive decision making requires additional reviews and or approvals, with an accurate record of the final decision.
3.4

Exception and urgent decisions

Getting started
  • Identify when a decision represents an exception to normal practice
  • Record the reason for the exception, who approved it and whether follow-up is required
  • Avoid allowing urgent decisions to remain completely undocumented
3.5

Decision documentation and evidence

Getting started
  • Record key decisions in a simple form, using existing tools where possible
  • At minimum, record what was decided, who approved it and when
  • Keep information relied on for the decision together with the decision record where it is necessary to explain or evidence the decision avoiding reliance on chats, verbal arrangements and other informal arangements
3.6

Governance and review

Getting started
  • Assign one person or function to maintain the company's decision-making framework
  • Define who approves changes to decision categories, approval routes and escalation rules

More situations

All 11 situations