AI & Technology

Building a Governance Platform Every Organization Can Make Its Own

Stratija

TailoredTo Each Organization’s Way of Working

10Workflows Running on One Rules Engine

200+Design Decisions Logged and Traced to Code

The Challenge

Uruk Project Management came to Innavera with a methodology, not a feature list. Its Value Delivery Methodology, refined over 20 years of consulting, defines how projects move through stages and gates, who may decide at each gate, and what every deliverable must contain. It lived in books, templates and workshops. Uruk wanted it to run as a commercial software product.

The rules were the hard part. Ten workflows across four project classes each carry their own stage path, gate numbering and deliverables. Some repeat delivery cycles. Some fork, with one gate approval opening implementation and an operations track in parallel. Decision authority shifts depending on whether a project has a sponsor, and terminating a project changes the state of every gate it never reached.

Tailoring was in the brief from day one. Uruk wanted every client organization to run the methodology its own way and in its own vocabulary, and that set the central design problem Innavera had to solve. Rigid tools force clients into the vendor’s process. Flexible tools let anyone change anything, so they enforce nothing. Stratija had to do both: let each organization reshape the methodology to fit, while the rules that make it governance still held.

The specification also kept moving. The methodology’s author refined his rulings throughout the build, across email threads and rounds of hands-on testing, so the platform had to absorb changes to its rules without being rewritten. And it had to ship as multi-tenant SaaS, with a decision record that would stand up to an auditor. Generic project management tools track tasks and dates; none of them can enforce decision authority or make a record immutable.

Our Approach

Innavera owned the build end to end: architecture, engineering, UX, quality assurance and release management. Five engineering decisions shaped the platform, starting with the one at its core:

Tailoring without losing control. Organizations start from ten ready workflows or from their own governance handbook. They clone a workflow into their own copy and rename every stage, gate and deliverable to the vocabulary their teams already use. They add the sections a project needs and hide the ones it does not, and hidden content is always restorable. Each project picks its workflow and its delivery mode: sequential, iterative or incremental. Tailoring changes the words and the shape, never the controls. A renamed gate still needs the right person’s written decision, and one organization’s changes never move another’s projects.
Workflows as data. Tailoring at that depth is only possible because each workflow is a definition, not code: stages, numbered gates, deliverables, sections and guidance text. A project’s entire structure is generated from its workflow when the project manager selects it. The same engine runs every delivery mode, and gates that open two stages at once. The catalogue grew to ten workflows during the build without new screens.
Governance enforced in the data layer. Gate decisions are immutable at the database level. The platform refuses to let one person act as both sponsor and project manager on the same project. Permissions are checked on every API request across six roles and additive grants, and consequential actions write to an audit trail.
A multi-tenant SaaS foundation. Cross-organization data isolation, a platform administration console, licence seat enforcement, and a user lifecycle in which disabling an account ends its live sessions.
A product people can work in. A mid-build UX redesign introduced a design token system, shared component primitives and new navigation. Deliverables auto-save, keep a version history per section, take attachments and export to PDF, as does the gate approval record.

Innavera also led Stratija’s go-to-market: planning, positioning for PMO buyers, the stratija.com launch site, commercial and service-level terms, and the launch itself.

Ready to put AI to work for your organization?

From strategy to deployment, we help you harness AI and emerging technology to drive measurable outcomes.

Start a Conversation

The Results

Stratija went from an empty repository to a multi-tenant SaaS platform in early access at stratija.com. Clients get a methodology that fits them from day one. An organization with no formal process starts governing its first project immediately. One with its own governance handbook turns it into rules the platform enforces, in its own vocabulary, so the handbook stops being a document people have to remember.

Because the methodology runs as configuration, changes to its rules land as data changes rather than rebuilds. The author’s rulings were absorbed throughout the build without reworking the product, and the workflow catalogue grew while the code stayed on one engine. The same architecture is ready to extend beyond project management into program management, executive dashboards and localisation.

The platform’s guarantees are enforced below the interface, in the database and the API. A gate decision cannot be edited or deleted, decision authority cannot be bypassed, and one organization cannot see another’s data. Every ruling behind the product is traceable from the decision log to the code to an on-screen verification, so the client takes a product to market with a complete engineering record behind it.