How Oridian decides, assigns and controls the work.
Before a requirement becomes an engagement, it has to be understood, scoped and found viable. What follows is the sequence that gets it there and keeps responsibility visible once delivery begins.
What the work is, and how it is run.
Solutions
Work Oridian organizes, performs or manages.
Approach
How Oridian decides, assigns and controls the work.
Before the work begins, the engagement must be viable.
Not every requirement should be accepted in its original form. Before committing to delivery, Oridian evaluates whether the work can be performed competently, lawfully, securely and within the required capacity. Where those conditions cannot be established, the requirement may be revised, deferred or declined.
Four stages, and what each one settles.
- 01
Understand
Define the objective, context, constraints, people, systems, jurisdiction and consequences of the work.
- 02
Design
Establish scope, responsibilities, acceptance criteria, team structure, workflow and supporting technology before delivery begins.
- 03
Deliver
Execute the work under the agreed controls, maintain evidence and keep responsibility visible throughout the engagement.
- 04
Improve
Correct confirmed problems, learn from delivery evidence and strengthen the process, controls, people or supporting technology where the findings justify it.
The controls the work is held to are published separately.
Oridian’s Quality Policy establishes the framework and baseline controls for quality, control and evidence. Each engagement determines how those controls apply to the requirement, including the relevant acceptance criteria and evidence.
Read the quality policyTechnology supports the engagement. It does not replace the service definition.
Which systems an engagement runs on is decided as part of the work. Oridian using its own infrastructure to deliver a service is not the same as the client adopting a product.
Client-owned systems
Oridian can deliver work within the systems a client already uses when those systems can support the agreed operating model, access requirements and delivery controls.
Oridian operational infrastructure
Oridian may use its own internal platforms to coordinate, control and evidence service delivery without turning the engagement into a software purchase by the client.
Oridian products
An organization may separately adopt an Oridian product when a repeatable platform fits its own operating requirement; product licensing and full platform information belong in Products.
Purpose-built technology
Oridian may design or develop technology for a specific requirement when existing systems and available products do not adequately support the required operation.
The form of delivery depends on the responsibility Oridian is expected to carry.
Five distinct structures cover how an engagement can be arranged. They are not degrees of one another, and which applies depends on the scope agreed for the work.
Explore delivery models in SolutionsStart with the requirement, not the method.
Describe the outcome, the constraints, the people and the systems involved. Where the work should be anchored is Oridian’s question to answer.