Technology operating model and governance
Clearer accountability, fewer uncontrolled changes, less disruption in production and a release process your team can repeat. Decision rights, environments, release management and change control are set up on the tools you already use, then run by your team or ours.
- Typical length
- Seven to eleven weeks, discovery included
- Covers
- Environments, release management, change control, access and ownership
- Investment basis
- Fixed price discovery, setup confirmed after it
01 In practice
Who decides what
Example. The actual design is set during discovery.
| Change | Requests | Approves | Releases |
|---|---|---|---|
| Content or data change | Business user | Business owner | Admin team |
| Configuration change | Business owner | Technical owner | Release manager |
| New integration | Technical owner | Change board | Release manager |
| New system or retirement | Executive sponsor | Executive sponsor and change board | Release manager |
02 Who it is for
- Systems that are changed directly in production
- Several vendors or internal teams changing the same platforms
- Platforms that grew quickly and now have unclear owners
- Boards or funders asking how technology change is controlled
03 What you get
- 01
Ownership register
Every system, its business owner, its technical owner and its support arrangement.
- 02
Environment strategy
Development, test and production environments, and what may move between them.
- 03
Release process
Gold copies, parity checks, release records and approval steps, in use from the first release.
- 04
Change register
One record of every change, its approver and its rollback.
- 05
Decision rights
Who approves what, at which level, written so it can be followed.
- 06
Handover
Templates and a walk through so your team can run it without us.
04 Investment
Indicative investment
Canadian dollars, before tax. Confirmed after discovery, based on complexity, integration requirements, delivery scope and your environment.
Scope assumptions. The lower end is one platform and one delivery team. The upper end is several platforms, vendors and teams sharing one release process.
05 How we deliver
One consistent approach, set for this work
Discover
Interviews with owners and vendors, a review of how changes reach production today, and the gaps that matter.
Build
Environments, registers, templates and approval steps set up on the tools you already use.
Release
The first releases run through the new process with your team, then adjusted.
Run
A handover to your team, a fixed transition period of close support, or a monthly service with release management as a service.
06 What we need from you
- An executive sponsor who can settle ownership questions
- Time with each system owner and vendor
- Read access to the platforms and the current change records
- Agreement on which tools the registers live in
07 Start
Discuss your project
Tell us what needs to change and when. If the work fits, we propose a fixed price discovery.