A bottom-up approach starts with the needs, concerns, and lived experience of people affected by a digital identity system. In practice, it uses local context and community input to shape design choices, rather than assuming the technology should lead the programme.
What a bottom-up approach changes in identity programme design
A bottom-up approach changes the starting point for design work. Instead of treating a digital identity system as a purely technical rollout, it begins with the people who will live with the rules, exceptions, and friction every day. That shift usually produces more usable enrolment, recovery, support, and access processes because the system is shaped around actual operating conditions.
The method is especially useful where identity decisions affect different communities differently. A design that looks efficient from a central programme view can fail locally if it ignores language, device access, digital literacy, shift patterns, or administrative realities. Bottom-up thinking helps surface those mismatches early, before they become adoption problems or workarounds.
Why local context matters
Local context is not a soft extra, it is often the difference between a working identity control and one that people avoid. Rules for proofing, authentication, reset, approval, and escalation can all behave differently once they meet real service conditions. A bottom-up approach looks for those points of friction before they become policy failures.
This is also where trust is built. If affected users, operators, or community representatives can see that their experience shaped the programme, the identity system is more likely to be understood as legitimate rather than imposed. That matters in environments where identity controls affect access to public services, employee workflows, partner onboarding, or population-scale platforms.
How bottom-up design improves control decisions
Bottom-up design does not replace standards or governance, but it can improve how they are applied. It helps teams decide whether a control is genuinely proportionate, whether a workflow is too rigid for the risk it is meant to manage, and whether an exception path is needed for legitimate edge cases. In identity programmes, those choices affect onboarding, authentication, account recovery, and access review.
The most valuable output is often not a new policy, but a better fit between policy and reality. That can mean simpler user journeys, clearer ownership, fewer unnecessary escalations, and fewer shadow processes created to bypass the official one. The result is usually stronger compliance in practice, not just on paper.
For role and access design, Role Mining and Role Design Guide is a useful companion because it shows how role structures can be shaped around observed business needs rather than abstract assumptions.
Where bottom-up approaches help most
Bottom-up methods are most effective when the identity system touches diverse user groups, multiple business units, or communities with different access needs. They are also useful when a central team is trying to replace a legacy process that people currently work around. In those cases, design choices need to reflect lived experience, not just target-state architecture.
They are less effective when they are treated as a one-time consultation exercise. If community input is gathered only at the start and then ignored, the approach becomes symbolic. The practical value comes from feeding that input into design decisions, then validating the resulting process against the same real-world conditions that exposed the original problem.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OC-01 — Organizational Context | Bottom-up design depends on understanding stakeholder needs and operating context. |
| GV.OC-02 — Mission, Objectives, and Stakeholders | The term centers affected people and local concerns as design inputs. | |
| Recommendation — Define the identity programme around stakeholder context and operating realities before setting control choices. Map identity design decisions to stakeholder needs and programme objectives. | ||
| ISO/IEC 27001:2022 | A.5.2 — Information security roles and responsibilities | Local participation changes ownership and accountability in identity design. |
| Recommendation — Assign clear ownership for identity decisions across central and local stakeholders. | ||
| NIST SP 800-53 Rev 5 | PM-11 — Mission and Business Process Definition | Bottom-up identity design must align controls with actual business process needs. |
| PM-30 — Supply Chain Risk Management Strategy | Community and operational input can expose dependency and governance weaknesses in deployed systems. | |
| Recommendation — Align identity processes with the business workflows they must support. Use stakeholder input to identify weak points in the identity delivery chain. | ||
Related resources from NHI Mgmt Group
- How should security teams respond to bottom-up SaaS adoption that bypasses procurement and expands access to company data?
- When should organisations use a blended top-down and bottom-up risk assessment instead of relying on one model alone?
- What is the difference between a top-down and a bottom-up IT risk assessment?
- What should teams do when their current password hashing approach may not hold up in a few years?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org