Ten methods, four project classes
Ten methods across Single-Stage, Micro, Small-Simple and Medium-Large, each with its own stages, gates and deliverables.
The platform
The vision, and what runs today.
The Uruk Framework is where Stratija is going. Below it, the six things the product does today. Every block on this page says which of the two it is.
The six principles Vision
Six principles the whole thing is built on.
Published in the Innavera and Uruk white paper From Practice to System, August 2026, and reproduced here word for word.
-
01
Project management is a core organizational function, requiring leadership, ownership, and investment, not a support activity to be delegated.
-
02
Governance is the backbone of decision-making, not an administrative burden.
-
03
Methodology must be adaptive and tailored, responsive to change and designed for context rather than dogmatic.
-
04
Value delivery requires integration across strategy, operations, and delivery, not fragmentation. Projects are investments and exist to deliver outcomes, not only outputs.
-
05
Organizational success must be predetermined, cultivated, and assessed, not accidental.
-
06
Capability requires the integration of People, Processes, and Technology. No single dimension is sufficient.
The Uruk Framework Vision
The framework is the whole; the methodology is one thing inside it.
Stratija is built on the Uruk Framework. The Value Delivery Methodology is the methodology inside that framework, and it is the part the platform runs today. The framework is wider: it holds strategy, portfolio, product, program and project work, the supporting actions that run beneath all of them, and the governance over the whole.
That distinction is the reason this page has two halves. What the framework describes is the destination. What the product does is below.
The Uruk Nexus Vision
One core, six elements, three rings.
The Nexus is how the framework fits together. The methodology sits at the core. Six elements connect into it: Strategy Formulation, Portfolio Management, Product Management, Program Management, Project Management and Supporting Actions. The People System wraps them on the inside and Community and Support on the outside, with Governance as the umbrella over all of it, because governance is embedded in every element rather than standing beside them.
Project Management is the element the platform runs today. The other five are where it is going.
What runs today Runs today
Everything below this line is in the product.
Six things it does, and what each one gives you. Nothing here is hedged and nothing here is coming later.
Methods and selection Runs today
Pick the method that fits the work.
The method is a choice you make once, at the start. Everything the project needs is built from it.
Sequential, iterative or incremental
Choose whether a method runs its stages once through or repeats a delivery cycle. The project is built with the stage path that matches.
Chosen once, by the project manager
The project manager picks the method once the project is active, and it cannot be changed afterwards. That project's stages, gates and deliverable shells are generated from the choice.
Stages and gates Runs today
A stage opens because somebody approved a gate.
Not because the last stage finished, and not because a date arrived. Every gate is a decision with an owner, a fixed set of outcomes and a written reason.
A stage path per method, and it forks
Each method carries its own stages and its own numbered gates. Four on the smallest method, eleven on the largest, plus an activation gate on every project. Most stages follow the one before them. On the methods that carry an operations track, one gate does not: its approval opens two stages at once, and the operations track runs alongside implementation from there rather than after it.
Parallel operations track
On the methods that carry one, an operations track runs alongside implementation. The same gate approval opens both.
A fixed decision set, and a reason
A gate decision is picked from the set that belongs to that gate: approve, revise, hold or terminate. The final gate offers approve or revise. No decision is recorded without a note, approvals included.
Gate Approval Record as PDF
The approver writes the criteria the decision is judged against, at the gate, and they print on the record beside the decision, the reason, the author and the date. Download it and hand it to an auditor.
Deliverables Runs today
Documents that guide as you fill them.
A deliverable arrives with its sections already outlined, and the Coach's guidance on most sections across the set.
Deliverables with established sections
A deliverable opens with its real sections in place, so a Project Brief asks for what a Project Brief holds instead of for free text.
Coach guidance in the form
Where the Coach has guidance for a section, it sits beside the field. Whoever is writing can read what the section is for without leaving the page.
Auto-save and version history
Work saves as you go, with nothing to remember to press. Every submitted section keeps its earlier text, and anyone who can read the deliverable can open its history with the author and the time.
Attachments, replace and remove
Attach files to a deliverable, replace one with a newer file, or remove one. The uploader and the date are recorded either way.
PDF export
Export a deliverable as a PDF when it has to travel outside the platform.
Tailoring Runs today
Start on day one, and keep tailoring.
Organizations with no method of their own start on day one with well-established methods we created. Organizations that prefer to tailor further find it easy, and never start from scratch.
Clone a method and rename it
Clone a built-in method into one your organization owns, then rename its stages, gates and deliverables to the words your teams already use. Nobody else's projects move.
Add sections, hide sections
Add a section to a deliverable on a project that needs one, and hide a section you do not use. Hidden, never destroyed, and restorable afterwards.
Organizational learning Runs today
What one project learns, every project can read.
A lesson is worth writing only if somebody else finds it. So lessons leave the project that produced them.
Cross-project lessons
A lesson written at the close of a stage is readable from every project in the organization, with a filter by project.
Portfolio-level summary
See how many lessons the organization holds, which projects contributed them, and which projects have contributed none.
Internal Knowledge Portal
Publish your organization's own reference material inside the platform, beside the projects it applies to, with its own administrators.
Administration Runs today
Who may do what, and what happened.
Permissions are checked on every request, and the consequential actions leave a record.
Six roles, plus additive grants
Six base roles on a project, plus separate grants such as knowledge-portal administration that sit on top of a role.
Organizations and user lifecycle
Create users, assign their roles, and disable an account. A disabled user is signed out of existing sessions and cannot sign back in.
Audit trail
Consequential actions are recorded against the project and readable by the people accountable for it.
Notifications
People are told in the product when something is waiting on them, such as a gate that needs a decision.
Project reporting
A project-level report brings the stages, the gates and the state of each deliverable onto one page.
Be part of the first release.
Early access is limited while we roll out the MVP.