Design your ideal systems. Change your business.
System design begins with the present business reality. It considers the people involved, current capabilities, desired future, and problems standing between them.
Our work may design the business system, a computer system within it, or both.
On this page
Before softwareSuitabilityMaking the system visibleDesign on its ownWhen the design is readySystems in practiceBefore software
We study the people, roles, needs, desired experiences, information, decisions, authority, processes, and technology. We also study exceptions, recovery, risk, governance, and security. This view shows what the proposed system must serve and what the change may affect.
The review also considers the proposed change's cost, financial viability, projected financial return, and fit within the business's financial model.
Suitability
The question is not whether a design is technically impressive. The question is whether it fits the client's situation, desired future, people, constraints, risks, resources, and capabilities.
Custom software is one possible result. Existing software, an integration, a process change, a hire, a delay, or no new build may be the suitable next action. No computer-system change remains a valid conclusion throughout the engagement.
Making the system visible
The method moves from understanding the business situation to formalizing what matters for the decision. An ontology may establish shared meanings between the business and engineering. A context graph may show the design from a particular point of view. A blueprint may make a proposed build visible before implementation.
Technical specifications define the requirements, security, cost, and risks needed for responsible construction and maintenance. Prototypes make the proposed system tangible enough to test the direction, expose changes, discover edge cases, build agreement, and decide whether further investment is warranted. Transition plans explain how change may affect the business and how it could proceed.
These artifacts are tools, not a fixed package. /prznt uses each one when it serves a clear purpose in the engagement.
Design on its own
System design can stand alone when it includes a suitable review of the client's prior planning. If the work exposes a missing policy or strategic decision, /prznt and the client decide how to address it.
When the design is ready
The design is ready when the client and /prznt understand the next action and agree that the engagement's readiness conditions have been met. Handoffs, protections, approval checks, and operating safeguards are designed for the receiving team and the risks involved.
The client leaves with a shared understanding of the current reality, desired future, affected people, proposed system, risks, and next action.
Systems in practice
Connected information, decisions, and actions across a business.
Alaïa
A business management system that connects relationships, commitments, projects, time, and agent activity. Models help turn brief notes into proposed tasks. Agents use connected tools to read records and carry out assigned tasks. Alaïa keeps assignments, results, and reviews together.
Better Hoops
A blueprint for how a basketball program connects people, information, and decisions. Agents helped develop the design from reviewed source material. The blueprint defines what people can see and do, and where an agent would need permission.
Change capabilities. Change results.