The final collection is Development, beginning with how the entire system is structured.
This includes:
— High-Level Requirements (HLRs)
— System-Level Agreements (SLAs)
— Test-Driven Development (TDD)
— Behaviour-Driven Development (BDD)
— Functional & Non-Functional Requirements (NFRs)
— User Acceptance Criteria (UACs)
These documents frame the technical parameters of each release.
Over the years, many development teams have shared how much they benefit from the transparency and consideration of this structure. Linking APIs, scripts, security protocols, code repositories, and documentation through automation reduces complexity and fosters true cross-functional collaboration.
HLRs act as the starting point - they define the product and set expectations for methods and routines. I often encourage designers to question everything at this stage. Their integration depends on understanding the definitions that shape the infrastructure beneath their work.
SLAs and System-Level Requirements deepen this. Designers who read these documents gain a competitive advantage in problem-solving because they understand not only what they are designing, but what the system must support.
Information Architecture reappears here with a different meaning — a maturity test for the team. Ask each member to define IA. If the answers vary wildly, you have a clarity problem.
Backend documentation focuses on logic — how the system works, where influence is possible, and what constraints exist. Whether you have full-stack engineers or a specialised team, visibility matters.
Frontend engineers now operate closer to design than ever — often functioning as Creative Technologists. Their access to design artefacts accelerates alignment and reduces friction.
This section must always include links to real code, features, prototypes, and version histories. Tracking progress through tangible artefacts reinforces accountability and clarity.
However, teams must also recognise the impact of technical debt. Delivering new functionality without remediation creates unscheduled work and disrupts planning. Automated testing - unit, integration, regression - allows teams to focus on higher-value problem-solving rather than repeated manual testing.
