Tacitum [email protected]

Timing is everything…

…in strategy, organization, and work, and most of all in the temporary endeavors that carry your strategic intent through an uncertain environment. Yet the rules that run the clocks are rarely written down, so they live in the heads of busy people and break when those people are away.

Tacitum writes those rules down, then lets AI agents keep your portfolio in step with them, so that decisions arrive while they can still change the outcome. People keep the authority to decide. Agents do the work between decisions.

Tacitum is built to run inside your own environment and under your own law, and to turn responsibility into resilience at machine speed.

Request early access
Benefit
$0
€0
¥0
Risk
$0
€0
¥0
Outputs flowing down as inputsOutputs flowing up as inputsEscalation, skipping tiers and handled off-cycleNow
Every time a tier fires, its outputs become inputs to the practices on the tiers above and below it rhythmically. Escalations skip tiers and are handled off-cycle. Where the clocks fail to line up, decisions wait, and portfolios lose time and money, and sometimes cost lives.

The rules nobody wrote down

The work of the future is people and agents working in a loop. That loop runs on rules of timing that almost nobody has written down, and our mission is to make them explicit.

Imagine a company of 200,000 employees working in a loop with 2 million agents, or 20 million. Satya Nadella, the chairman and CEO of Microsoft, put that supposition to Reid Hoffman in June 2026. He then asked what tacit knowledge such a loop creates, and what artifacts pass among the agents and between the agents and the people. He said confidence will come when agents can be steered by human preferences and can stay the course, and that the work of the future is the tacit knowledge created by that interplay. Nadella expects that interplay to reach all knowledge work. We have been building Tacitum on that premise since 2021, leveraging twenty prior years of hands-on experience in the portfolios of Fortune 100 companies and equally esteemed government entities.

Wherever complex knowledge work is aimed at a result by a deadline, it is organized into projects, programs, and portfolios, and running them is knowledge work in every sector. Tasks are subsumed to projects that start and stop as required, adapting fluidly above the more stable organizational structures that spawn them. Those projects routinely span corporate boundaries, drawing people and resources from inside and outside the firm, so that they form adaptive networks within and between firms in which a newcomer to any endeavor may arrive from either side.

A portfolio of endeavors is only as adaptive as the governance that decides when to move it, and governance that cannot adapt its timing under pressure cannot contend with the very conditions that made projects necessary in the first place. Strategic problems now confronting all organizations (like heightened geopolitical risks, supply-chain fragility, exponential acceleration of artificial intelligence, the structural shift toward a sustainable and inclusive economy, demographic transformation and climate transition) generate precisely the complex, volatile conditions under which a portfolio of projects earns its keep. They can be initiated, accelerated, redirected, and terminated as conditions change (or as solutions to problems create other problems that require solutions), and a portfolio of them offers a form of temporal responsiveness that more permanent organizational structures cannot match. But converting that responsiveness into organizational value is not automatic. It requires governance that can time decisions reliably and synchronize action across the nested layers of projects, programs, and portfolios in step with the pace and pattern of disturbance.

Rules of timing pervade this fabric, and most of them are tacit: when a decision is due, who must make it, and what must wait for what. Our mission is to make those rules explicit and to provision the agents that assist every essential project, program, and portfolio management role, so that organizations can adapt at machine speed.

Most portfolio failures are failures of timing

Portfolios rarely fail for want of a decision. They fail because the decision arrived after its window had closed, and nobody owned how the calendars fit together.

A decision arrives after the window it was meant for. A program waits on a project that is waiting on a budget review. Every forum keeps its own calendar, and nobody owns how those calendars fit together. When conditions require everyone to pivot, the clocks are reset manually.

These timing failures are disconnects at one tier of management between selecting, prioritizing, and terminating endeavors. They are disconnects at another tier between ideating, composing, and measuring benefits. They are disconnects at another tier between governing, controlling, and learning from endeavors. Critically, they are disconnects across these tiers. Consequently, when disturbances arrive, the disturbances are not absorbed. Things break.

Many of these disconnects are hard to see, because what one practice owes another often does not travel directly. It passes through a third practice on the way. A lesson learned reaches the decision to stop an endeavor only after it has changed what the controls detect. The reason an endeavor was selected reaches the people who measure its benefits only through the business case. When the practice in the middle stalls, the practice at the end waits for something that is not coming, and nobody can see where it stopped.

The rules that would fix this already exist in your organization. They live in habits and in the heads of experienced people, which is why they break when those people are busy or gone. As AI agents take on more of the work, the gap widens, because an agent that does not know the rules acts on its own clock.

Imagine a world where AI agents continuously scanned the environment for disturbances, a world where those agents determined what was necessary at each tier of management, a world where they prevented disconnects between the people responsible for selecting, prioritizing, and terminating endeavors, ideating, composing, and measuring benefits, governing, controlling, and learning. Tacitum is being built to create that world.

You can test the claim against your own calendar before reading further. Take the last disturbance that cost your portfolio real money. Which forum would have caught it, how long did the catch wait for that forum's next sitting, and who, on the record, held the authority to act sooner? Where were the rules that would have prevented those issues in the first place? Resilience requires more than improvisation.

One escalation, end to end

Follow one cost overrun from the moment an agent detects it to the moment a named person decides. The agents prepare everything, and at no point do they hold the authority.

A worked example, drawn from the self-assessment of a multinational manufacturer with names and figures changed. Each step names who acts: an agent, the synchronizing core, a person, or the gateway. The rule codes are the register's own.

Three of those terms are explained in full further down. The register is the organization's own timing rules, written down and approved by the people who own them. The synchronizing core is the code that checks every agent action against the register. The gateway is the one component that holds the credentials to write to a system of record.

  1. Controlling agent

    A forecast crosses the line

    At the biweekly progress review, the Controlling agent reads the ERP through a read-only connector: line 3's forecast is 12 percent over the approved budget. It drafts the change-log entry. It cannot act on it.

  2. Synchronizing core

    A register disposes of it

    Rule THR-21, owned by the head of investment control, absorbs variance below 10 percent and interrupts above 25. A 12 percent reading, held for one project cycle, is disposed wait: the core opens an obligation on the investment committee, due within one of its cycles.

  3. Synchronizing core

    Routed by the calendar

    The core routes the item the same day. Where it goes is this organization's own choice: its rule sends a 12 percent variance to the committee's next monthly sitting, and above 25 percent the same rule would call an off-cycle sitting. Any wait belongs to the rule, and the rule belongs to you.

  4. Composing and Prioritizing agents

    Options, not decisions

    The Composing agent drafts two options and flags the coupled project. The Prioritizing agent may note a re-ranking but may not enact one: no rule grants mid-year authority, so the core withholds the action.

  5. Committee chair

    One person ratifies

    Everything the chair needs was ready on Day 0. This organization's rule set the decision for the next sitting, and a different rule would have set it for the same day. The chair ratifies option A. Who decided, when, and under which rule are recorded and content-addressed under UOR-ADDR, so the decision can be proven later.

  6. Gateway

    Executed at your speed

    The gateway writes the ratified baseline to the ERP and records the tool's reply.

  7. Measuring and Learning agents

    Learned, automatically

    The Measuring agent resets the benefit baseline; the Learning agent files the lesson against the trigger that caused it.

Seven records, one chain. The agents never held authority over the baseline; the chair did, on the record.

Before an agent can be trusted with a portfolio

An agent can be trusted with a portfolio only when it knows your real rules, acts within authority that a named person holds, leaves a record that can be audited, and runs under your law.

Four things have to be true.

  • It knows the organization's actual rules: which forums decide what, on which cycle, and what triggers an escalation.
  • It acts only within authority that a named person holds, on the record.
  • Every change to a rule is proposed, approved by a person, and logged, so the system can be audited after the fact.
  • It runs under your law. The computing, the models, and the records sit inside your own environment, and nothing crosses the boundary that you did not list.

Few organizations meet the first condition, because the rules were never written down. Few vendors meet the fourth, because most agents call a model that someone else runs, somewhere else. Tacitum starts with the first and is built for the last.

How Tacitum works

You assess how your portfolio actually keeps time. You approve the register of rules that results. Agents then work inside those rules, in your own environment.

  1. Assess

    A guided self-assessment captures how your portfolio is actually governed: which forums meet, how often, what triggers an escalation, and who decides. Tacit rules that sit silently in the data of your projects, rules which have never been written and which may be unknown to those ruled by them, emerge from their hiding places to form a clear picture of how you really work. This is not a survey of people’s opinions. It is a guided discovery of your organization’s records, which becomes automated forensics. You do not need mature governance or a written rulebook to begin. The assessment identifies both your tacit rules and your missing rules, and for every gap Tacitum proposes a rule that fits the way you already work.

  2. Register

    Each person knows a piece of those rules, but nobody sees the whole. Tacitum assembles the pieces from the artifacts your people already keep, and the result works like a Rosetta Stone, translating the strategy your leaders state into the timing your portfolio actually keeps. Any new rules you adopt raise your maturity level the moment you adopt them. Tacitum then registers the optimized set of rules, the ones you already keep together with the proposed ones you approve, in machine-readable form: rules for cadence, thresholds, and synchronization. Nothing enters the register without your approval, so what it holds is your own way of working. Every rule is visible, versioned, and owned by a named person.

  3. Operate

    Tacitum is not a consulting firm. Your self-assessment is the boot sequence for a suite of agents that you deploy inside your own environment, on premises or in a cloud tenancy you own. An AI agent for each portfolio practice, from prioritizing to controlling, proposes and carries out work. A synchronizing core checks every action against the register. That core is deterministic code, not a language model, so the rules hold even when a model errs. In a private deployment, every model the agents use runs on your own machines, and there is no switch that sends your work anywhere else. Your budgets, priorities, and unannounced decisions never leave your walls, and no one outside them, Tacitum included, can read them.

What the customer sees

Each agent prepares what its practice owes and a named person approves it before it goes anywhere. Decision papers, dashboards, and alerts reach your people in the tools they already use.

Most people in the organization will never know Tacitum is there. What they will see is the fruit of an orchestra of agents; they will notice human leaders across the organization's management levels all transforming into performers at the highest level. Each agent is paired with a named person, its human counterpart, and works for that person around the clock: it drafts everything its practice owes to the practices downstream of it, the person approves, and only then does it go. In plainer words, the agent is a companion that prepares; the person decides what leaves. The agent never gets tired and never sleeps.

For every project, program, and portfolio the dashboards, decks, budgets, schedules, memos and more are generated continuously from the systems of record, so no sitting waits on an input and every output is continuously up-to-date around-the-clock. Alerts are written for the person who needs them and arrive through the tools that person already uses, whether that is Teams, Slack, email, or a text message.

Tacitum is designed to follow each output along its whole route, not only to the next desk. When something you are waiting for has stopped two steps upstream, the alert is designed to say where it stopped and who holds it. Over time, Tacitum is designed to show where your organization's routes tend to break, which is something a tool that sees only direct hand-offs cannot show you.

Approval is designed to be a decision, not a click. For the outputs that matter most, those that bear on selecting, funding, or stopping an endeavor, the agents do not recommend. They lay out the options, the records each rests on, and the assumptions that would change the answer, and when the people those agents support take action the agents learn. Orchestration isn’t orchestration unless it is seamless, and that is a learned capability. That learning happens by considering data that is a byproduct of the day-to-day administration of your portfolios. That silent byproduct is a data lake that is swelling right now at rapidly increasing scale into a strategic weapon that Tacitum unlocks.

Who this is for

Tacitum is for everyone who runs a portfolio or depends on one, from the PMO leader to the investment committee to the security team. It is licensed per organization or portfolio, not per seat.

Everyone who runs a portfolio or depends on one. Governance is a shared function, so Tacitum is licensed per organization or portfolio rather than per seat.

  • The people doing the work

    Those who select, prioritize, and terminate the portfolio's endeavors; who ideate, compose, and measure benefits; who govern, control, and learn from each project and program. Each has an agent as a companion that drafts what the practice owes.

  • PMO or portfolio governance leader

    Establishes the rules, prepares decisions, tracks obligations, and coordinates the forums. The register is this role's instrument, and the first conversation is usually here.

  • CFO, CIO, or investment committee sponsor

    Wants investment oversight, escalation, and accountability that hold between sittings, not only at them.

  • Committee chair and investment control staff

    Receive complete decision packages before the deadline and exercise recorded authority when they decide.

  • Security, architecture, and risk teams

    Validate the deployment boundary, the permissions each agent holds, and the evidence the system leaves behind.

  • Ministries, utilities, defense and transit authorities, and regulated firms

    Need the agents, the models, and the records to sit under their own jurisdiction, and a statement of what runs where that their security team can test rather than take on trust. Those that answer to AI regulators in Europe or Korea, or to auditors applying the NIST or ISO standards, also need the evidence of oversight to come from the system itself.

  • Every stakeholder of every endeavor

    Sponsors, customers, suppliers, and team members of each project, program, and portfolio receive the papers, the alerts, and the decisions in the tools they already use, and can see who decided and under which rule.

What is different. Portfolio platforms record a decision after people make it, and approval workflows route a document without knowing the calendar or the thresholds. Tacitum holds the timing rules as an enforceable object that agents cannot bypass, inside an environment that no outside party can reach, and maintains a predictable capability grown to absorb disturbances. That design can be described in a paragraph. What fills it cannot be: knowing which rules to look for, and where an organization's records hide them, comes from having written the standard those rules descend from and from two decades inside the portfolios that keep them. Whether the result is faster and better-prepared decisions is a question of measurement, and the measures are stated below.

Agents can propose. Only people ratify.

No AI system can grant itself authority. Tacitum is built so that a person always holds it, on the record, and so that what each agent did can be proven afterward.

An AI system cannot grant itself authority over when decisions get made. Someone has to hold that authority, on the record, and answer for it. Tacitum is built around that requirement, and it is what makes an agentic portfolio governable.

Every agent action is designed to be provable, not merely logged. Each request, decision, ratification, and result is to receive a content address under UOR-ADDR, an open standard authored by our co-founder, so a customer can show afterward what each agent did and under whose authority.

What we measure

For every disturbance, the question is whether your portfolio absorbed it or amplified it. Tacitum is designed to record six readings that answer that question as each episode happens.

The unit of measurement is the disturbance episode: a cost overrun, a supplier failure, an engineering re-estimate, a directive from above. For each one, the question is whether the portfolio absorbed it or amplified it. The six readings below are the ones the research behind Tacitum uses to answer that question, and the product is designed to record them as each episode happens rather than reconstruct them afterward.

  1. Within the window

    Whether the authorized decision arrived by the time the disturbance allowed, not merely by the next sitting. That time is set by the disturbance and the work, not by the calendar. Missed windows are counted.

  2. Through the rules

    The share of episodes resolved by a pre-authorized path: absorbed within a bound, escalated per rule, or sent down the standing off-cycle path. The rest were improvised.

  3. Thresholds that fire

    For each episode, whether the written threshold fired, fired late, stayed silent, or never existed. A threshold that never fires is governance on paper.

  4. Baselines by approval

    Episodes that close with an approved change to scope, schedule, or cost, against those that close with an unapproved departure from one.

  5. Responses that hold

    Whether a decision stands or is reversed within a short interval, and whether a breach that keeps recurring leads to a rule change or to the same handling by hand.

  6. The cost of governing

    Staff time to prepare decisions and to maintain the register, and the share of committee items that arrive with their evidence before they are due.

Read together, these say whether a portfolio absorbs disturbance or amplifies it. Repeated reversals are thrash; nothing ever coming due is drift. The pattern we are after is governed flexibility: course changed quickly, through the organization's own rules, and the change holds.

Under your own law

Residency is where the servers are. Sovereignty is whose law reaches them. Tacitum's private deployment is designed so that your portfolio data, the models, and the records stay inside your environment.

Sovereignty is a word that procurement teams now use with precision, so Tacitum uses it the same way. Residency is where the servers are. Sovereignty is whose law reaches them. A service run by a company in one country does not become sovereign for a buyer in another by renting servers nearby, because the first country's courts can still compel the company that holds the data. For portfolio data, which shows what an organization is funding, delaying, and stopping before anyone has been told, the distinction is not academic.

Dependence on a model that someone else runs carries the same risk. In June 2026, export controls suspended access to two leading hosted models for about three weeks. The organizations that lost them had done nothing; the decision was made elsewhere, about something else. An agent that stops when a foreign authority says so is not an agent you can build governance on.

Tacitum's private deployment is designed to meet the test as a security team would state it. The agents run on open models, served on NVIDIA accelerated computing inside your own environment, from weights you hold. The synchronizing core is deterministic code and runs on CPUs. Every model call that the agents, the guard layer, and the evaluation make resolves inside your environment; the private deployment holds no credentials for any outside model service and has no path to fall back to one. That rule is written into Tacitum's security policy, and it admits no exception that a customer could switch on, because a switch a customer could turn on is a switch an attacker could turn on.

What leaves your environment is a short list, and the list is the contract. Portfolio records, agent memory, and artifacts never leave. Approval requests and alerts reach your own communication tools and carry no content, only a link back inside. Signed software releases come in, verified, and load only when your named owner approves. If you later choose to take part in federated learning, model updates and aggregate statistics leave through privacy filters under policies your own security team writes, and nothing else does. Every private deployment must ship with a sovereignty statement generated from the deployment itself, naming what runs where, what leaves and under what conditions, and how your security team can test each claim, with the tests included.

The agents reach the systems a portfolio already runs on through the Model Context Protocol, an open standard by which a system publishes what an agent may read and do. They never call those systems directly. Every request passes through the synchronizing core, which checks it against the register, and then through a gateway that holds the credentials and makes only the approved call, inside your own environment.

Tacitum also offers a hosted service for organizations whose requirement is residency rather than sovereignty; as an American company, Tacitum keeps data under United States jurisdiction for those customers, reserving a higher tier for customers whose operations require sovereignty, wherever they require that.

Built to the bar set for high-risk AI

Tacitum is designed to legal standards widely regarded as the most rigorous internationally for high-risk systems, without slowing you down, even where the law does not require it. The evidence a regulator asks for is what Tacitum produces by operating. In jurisdictions where regulators aren't asking for this, Tacitum provides it to its users directly anyway, for our customers to use as they see fit.

Widely recognized for its controls, the EU AI Act places duties on the organization that uses an AI system, not only on the company that built it. Where a system is classed as high-risk, the organization must put it under named people who have the competence and the authority to overrule it, must keep its logs, and must be able to show a regulator both. Those duties apply from December 2, 2027.

Most portfolio work will not be classed as high-risk. Tacitum is designed to that standard anyway. Every agent output goes to a named person who decides. Every decision is recorded so that it can be proven later. Every agent can be stopped. Approval is designed to be a decision, not a click, because the Act names the danger of people deferring to a machine. Tacitum measures practices and forums, never individuals.

The evidence a regulator asks for is therefore not a process you run after you buy Tacitum. It is what Tacitum produces by operating.

Europe is not alone. South Korea's AI Basic Act, in force since January 2026, requires human oversight and records for high-impact AI, and it reaches companies outside Korea. In the United States, where no federal statute exists, buyers and auditors ask instead for alignment with the NIST AI Risk Management Framework and with ISO/IEC 42001. These differ in scope and in force, but they ask for the same three things: a named person with authority over the system, a record of what it did, and a way to stop it. Tacitum is designed around those three, so one design answers all of them.

What to require of anyone who runs agents in your portfolio

Seven requirements separate governed agents from agents that merely run. Put them to every provider you consider, this one included.

Before you choose a partner for this, write down what you would require of any of them. Our list is below. Hold us to it, and hold everyone else to it.

  • Your rules, written down and owned by named people, before any agent acts, rather than a model's guess at them.
  • A core that enforces those rules in deterministic code, so that an error in a model is caught by something that is not a model.
  • Authority that stays with people, on the record, with every ratification provable afterward by anyone holding the ledger.
  • Agents that run inside your environment, under your law, with a tested statement of what leaves and nothing that leaves unlisted.
  • Measures that tell absorbing a disturbance from amplifying one, recorded as each episode happens rather than reconstructed later.
  • Learning designed to improve the thresholds and skills every customer starts from, without any record leaving the customer who produced it, and claims that stop where the build stops.
  • Evidence a regulator or auditor will accept. Ask whether oversight, logs, and the ability to stop an agent arrive as records the system produces, or as paperwork you assemble afterward.

Ask each provider you are considering which of the seven it meets today, and which it could add without rebuilding. Notice which qualifications are expensive to build and which ones can’t be bolted on afterward. Tacitum was built to put your rules first. They outlast the people who carried them in their heads, and they outlast any vendor.

Your rules stay yours. The learning compounds.

Your register is yours to read, export, and keep. What no single organization can assemble alone is a base of thresholds and skills designed to improve with what every deployment learns, while every customer's records stay home.

A register belongs to the organization that wrote it. You can read it, export it, and keep it if you leave, and that is deliberate, because a governance record that only its vendor can read is not governance. So a careful buyer asks the next question. If the rules are mine and the models run on my machines, what am I getting that I could not assemble myself?

The answer is the part that no single organization can produce alone. Every customer starts from a base of thresholds and skills, and that base is designed to improve with what every deployment learns: which thresholds fired too early or too late, which drafts the human counterparts edited or dismissed, and which handoffs between practices hold in the field. One portfolio sees only its own disturbances. The base is built to carry what has been learned from all of them.

For a private deployment, that learning is designed to travel without the records. Under federated learning, the model goes to the data instead of the data going to the model. Each participating site trains on its own records inside its own walls, and only a description of how the model changed and a set of aggregate figures leave, through privacy filters, under policies the customer's own security team writes. Taking part is the customer's choice and never a condition of sovereignty, and a customer who declines still receives every improvement to the base. In plainer words, your portfolio can teach the shared model and stay home.

What anyone building this would have to bring

Governed portfolio agents can be described in a page. Building them takes five things that are measured in years rather than in funding.

Governed agents for a portfolio can be described in a page. Building them takes five things, and each is measured in years rather than in funding. Check any provider against the list, this one included.

  • A model of the portfolio practices and of what each owes the others in time, calibrated in the field rather than inferred from documents. Without it, an agent cannot know what one practice owes another, or when. The model has to include the routes by which one practice's output reaches another through a third, because an agent that knows only its direct suppliers waits for inputs that arrive another way.
  • An instrument that draws an organization's unwritten rules out of its own records. People cannot report rules they do not know they keep, so asking them does not work.
  • A core tested before it touches a real portfolio, under an evaluation design registered in advance, so that the result cannot be fitted to the claim afterward.
  • The standing to be let inside. Portfolio records show what an organization is funding, delaying, and stopping, and they are opened to people with a long record of having been trusted with them.
  • A base that learns from every deployment without taking any deployment's records, so that what a customer runs next year knows more than what it started with.

Tacitum's model of the practices comes from the global standard that its co-founder John Schlichter led about 800 practitioners in 35 countries to write, and from more than two decades inside the portfolios of global organizations. Its instrument is the assessment platform, which is in production now. It is built on twenty years of intellectual property, all of which Tacitum owns, and it is the newest in a line of assessment instruments he has fielded across sectors. On top of that, Tacitum provisions a proprietary rules engine that compounds learning continuously.

Where Tacitum stands

The assessment platform is in production. The governance core is being tested in a simulated portfolio. The first practice agent is scheduled for early 2027, with pilots from mid-2027.

  • The design rests on institutional standards that govern a multi-trillion-dollar economy of temporary endeavors, standards our co-founder John Schlichter originated and that have been adopted globally for decades.
  • The assessment platform is in production and in use with a multinational manufacturer. It is built on twenty years of intellectual property, which has been transferred in full to Tacitum.
  • The governance core is being tested in a simulated portfolio, under an evaluation design registered in advance.
  • The agent layer is designed, with the first practice agent scheduled for early 2027 and pilots with outside organizations from mid-2027. That means right now is the best time for your organization to use Tacitum's self-assessment tool if your organization wants to create the possibility of piloting agentic PPM mid-2027.
  • Tacitum has not undergone a conformity assessment under the EU AI Act. The first pilots are planned ahead of the date the Act's high-risk duties apply.
  • The sovereignty rule for private deployment is written into Tacitum's security plan, November 2026, together with the measures that keep approval from becoming a formality.
  • Route tracing, which follows a hand-off through the practice in the middle and reports where it stalled, is designed and is to arrive with the agent layer.
  • The learning loops that improve the base every customer starts from are designed and begin with the first pilots, with federated learning as the route by which private deployments are to take part.
  • Tacitum is a member of the NVIDIA Inception program, accepted in November 2026.
  • AWS is providing compute credits through its AWS Activate program, which Tacitum is using to iterate development of the agents.
  • Tacitum supports the AI Portfolio Management Survey, a study of portfolio governance under AI acceleration, which is in the field now.
  • The research behind Tacitum is being prepared for peer-reviewed journals in information systems.

Start with how your portfolio keeps time

The first step is a self-assessment that produces the register of your organization's own rules. We are looking for a small number of PMO and portfolio leaders to take it now.

A self-assessment is the first step. It works from your records rather than your opinions. It is a rigorous assessment that requires more than one sitting from a PMO leader or someone familiar with your organization and its portfolio management approach. You can complete the assessment incrementally, at your own pace. What it produces is not merely an assessment but the register of your own organization's own rules, the rules it keeps even if those rules have never been written, and even if those governed by the rules never knew they existed. That is infinitely more valuable to you than a maturity assessment report. We are looking for a small number of PMO and portfolio leaders to take the self-assessment now, and for a smaller number whose security teams will hold the private deployment to the list above when it ships. Write to [email protected] to take part. Meet the leadership team.