FAQs

You Have Questions?

Here are answers to many of them.

Frequently Asked Questions

We've compiled a list of answers to common questions.

Contextuum in brief

Contextuum is a strategy activation platform. It converts an organization’s strategy from prose into structured data, then works in two directions: outward, into the everyday decisions employees make, and inward, bringing evidence from those decisions and from the wider world back to leadership so the strategy can be tested and renewed.

Most strategies are formed at an event — a retreat or a planning season — and then broadcast. Contextuum gives the strategy a working form: one people can decide with, and one that can be checked against the conditions it depends on.

Strategy activation is the state in which a strategy is actually in action: Actively considered in the decisions people make; Actively being tested by assessing new evidence and feedback; In action, renewing itself based on changes in the conditions or new feedback. Strategy execution is about getting work done. Activation is about the strategy being the context that decides which work gets done, and how.

An activated strategy shapes the thousands of everyday calls no one escalates: which customer request to honor, which project to drop, when to hold the price, how to choose between two competing priorities. A strategy can be brilliant and still inactive.

Contextuum has two directions of flow. In one, the strategy that leadership forms travels outward into employees’ decisions. In the other, evidence travels back— anonymized patterns from employees’ work, plus changes in outside conditions — giving leadership new input with which to revise the strategy (or leave it as is). A revision then flows outward again in its renewed state.

Most organizations manage the first direction imperfectly and the second hardly at all. The strategy fades before it reaches the moment of decision, and evidence about whether it still holds arrives as results, after the fact, or waits for the next planning cycle. Contextuum is built so neither direction ends when the strategic planning event does.

Contextuum serves two different leadership needs. Leaders who craft strategy need to be able to revisit it and determine whether it remains valid. Contextuum fills that need by providing evidence for the existing strategy—whether it still holds, or that something has changed and it holds less well — or that it could be even better at exploiting new opportunity.

Leaders who execute the strategy need to ensure that their teams understand the strategy and how it affects their own work; that their decisions and behavior are both faithfully guided by the strategy. Contextuum fulfills that need by providing a structure to help team members understand how to use the strategy in their own, specific jobs and how to apply it to difficult choices they encounter in the course of the day.

Chiefs of Staff, strategy leads and outside consultants often set up and run the platform on a leader’s behalf. Organization size matters less than whether there is a strategy that people are meant to act on.

OKR and KPI tools measure outcomes; Contextuum works on the choices and reasoning that produce them. Your OKRs show where you’re aiming and your KPIs show what you’ve done. Contextuum is the compass people use to navigate moment by moment. It complements your dashboards rather than replacing them.

A metric can be hit without the strategy being activated and considered in decision-making. Metrics don’t tell anyone which way to go when a product priority and a customer request collide. Integration that connects strategic context to performance platform data is coming.

Not in the usual sense. Strategy creation tools help build a strategy, execution tools track progress against it, and communication tools broadcast it. Contextuum gives the finished strategy a working form that carries it into decisions and carries evidence back — so it doesn’t create your strategy, and it isn’t a measurement dashboard. But it uses your strategy and your measurements to inform decision-making and strategic iteration.

Contextuum does not judge whether a strategy is good. It captures the strategy you have, helps people decide with it, and reports what it finds. What to do about any finding is always leadership’s call.

The foundation: your strategy as data

In Contextuum, a strategy schema is your strategy converted from prose into structured, query-able data: vision, mission, core values, strategic priorities, trade-offs and decision-making principles, along with the reasoning behind them. Every other part of the platform runs on it. (This is unrelated to schema.org website markup.)

A document gets read differently by every person who opens it. A schema can be used by AI in a consistently repeatable way. That means it can be used to generate an infinite number of potential dilemmas that may demand the working judgment of thousands of people at once and be checked against the world it depends on. It keeps the nuance. Contextuum’s AI can extract rationale and texture, not just a list of goals.

Some or all of: strategy documents, slide decks and transcripts; URLs for your website and strategy documents; and as much or as little as you choose of an in-depth guided dialogue. Contextuum extracts your strategic framework from whatever you provide and structures it into a schema.

You can add depth at any time through advanced dialogues: Competitive Positioning Matrix, Jobs to be Done Analysis, Multiple Scenarios Planning, Long-term Vision Mapping, and Results Backtracking (Merlin method).

Hours, not weeks. A working schema takes between 20 and 90 minutes. The range depends on what you bring. A comprehensive strategy document or URL supplies most of what Contextuum needs, so the guided dialogue only fills the gaps; with a thin document or none, the dialogue does more of the work. A strategy with many priorities, trade-offs and decision principles also takes longer, because each is captured along with the reasoning behind it. The Core Interview, completed by the strategy owner, is separate and takes 20–50 minutes. The advanced dialogues add depth and can be spread across sessions, but they’re optional. There is no IT integration, no installation, and no configuration project.

Once the set-up and the Core Interview are complete, employees can start the Strategy Introduction immediately.

The Core Interview captures how your strategy is actually managed: how much latitude team leads really have, when a decision must go up the chain, and what gives when the quarter is at risk. It must be done by whoever has the most at stake in the strategy’s success — the CEO, founder or owner. It takes between 20 and 50 minutes depending on the user.

Documents say what the strategy is; the interview captures how it’s run. Employees never see the specific answers that were given to any questions, but they may see its extracted principles if visibility is enabled. However, they meet it in their Strategy Introduction scenarios, as the difference between a call they should make themselves and one that belongs with their supervisor. The Core Interview is required before the Strategy Introduction and Praxis.

Yes, with one exception. Your team, consultant or coach can handle the documents, the advanced dialogues and the collaborative sessions, provided they know the strategy intimately. The Core Interview must be done by the strategy owner, because no one else can say how that person actually parses clashing priorities except the person who will make those calls.

Outward: strategy into decisions

Usually not because they don’t know it. In the moment, when they must make a choice or act, it is that decision, the project, the customer or the metric that is on their mind—not the strategy. Values and KPIs don’t say which way to go when two good options collide, so people choose based on expedience or based on whatever other pressure is compelling at that moment. Contextuum builds the judgment as muscle memory through practice making the decisions that are typical in their own role.

Town halls, emails, scorecards and training get the strategy heard. But they remain conceptual. On an ordinary Tuesday afternoon, they are an abstract memory, not a standard to apply.

The Strategy Introduction is an on-demand, AI-generated, role-specific experience that teaches people to think from the strategy. Each person works through realistic scenarios matched to their job and chooses the most strategic path. It consists of around 30 individual interactions. Each presents a realistic scenario from the person’s role and a set of possible responses. Depending on the role, how fast someone reads, and how quickly they process the details, the introduction can take from 20 to as much as 60 minutes. The more senior the role, the more nuanced the scenarios and the closer the choices, so senior people tend toward the upper end. A passing score unlocks Praxis.

Scoring is not right-or-wrong: every scenario has a best answer, a worst answer, and two in between. Every attempt generates new situations, so there is nothing to memorize. The shift is from “I know what the strategy says” to “I can judge what’s most strategic.”

Praxis is Contextuum’s ongoing strategic dialogue: AI thinking tools, with built-in mental models and heuristics, for the hardest situations people face at work. It has four modes — Decision-Making and Problem-Solving, available now, and Resolve Strategic Conflicts and Strategy AMA, coming soon.

People bring the problem in front of them, not the strategy: a customer request that conflicts with the roadmap, two projects and budget for one, a pattern in complaints. Praxis helps them work it through using your strategy as context. Decision-Making produces a well-reasoned, strategic decision; Problem-Solving produces a clear problem definition, evaluated options and high-confidence solutions.

Everyone. The leadership team uses the same Praxis tools as a store manager. Scenarios adapt to role and context, but the capability is universal. It isn’t training; it builds the skill of thinking critically from the strategy.

No. Praxis content stays private to the person who wrote it. The leadership dashboard shows nothing about Praxis at all — it reports Strategy Introduction progress only. Employee input reaches Strategic Radar solely as anonymized, aggregated patterns and themes. Because of the need for genuine anonymization and statistical significance, Praxis is only utilized in Strategic Radar for organizations with 50 or more active users persisting over at least 90 days.

Inward: evidence back to the strategy

Through two modules. Strategic Radar reports what is changing in the conditions your strategy depends on. Diamond Mine surfaces what your strategy isn’t yet using. Both produce findings, not advice: leadership decides whether and how to act.

Both live in the Findings Module, where their scans are run and their findings are read. The Findings Module is the part of the platform that beta approval unlocks.

Strategic Radar watches the conditions your strategy needs in order to succeed and reports movement in either direction — what is turning against the strategy and what is opening in front of it — while there is still time to act. Most leaders otherwise learn their strategy needs attention from quarterly results.

It reads two or three degrees out from the obvious news, so what surfaces isn’t what every business-press reader already knows, and it never reports an event without its consequence. Reviews can be scheduled monthly, quarterly or on demand. “Nothing to report” is a real answer.

Three possible sources (depending on the organization and its choices).

1) Environmental scanning covers relevant news, competitive and market movements, technology and regulatory shifts, and emerging opportunities and threats.

2) Your team (once there are 50 active users sustained over at least 90 days) contributes anonymized patterns from their work. Their use of Praxis is anonymized and analyzed for trends and underlying condition changes.

3) Leadership also shapes what Radar watches. Leaders can add entirely new conditions — a technology shift they suspect, a constraint they sense coming — and revise or remove the conditions that Contextuum found. A condition a leader adds becomes one of the items that Radar scans against on its next pass.

Team signals include customer behavior in pitches and help desk interactions, up-sell opportunities, new feature demand and new pipeline potential; market shifts; operational friction where strategy meets reality; and strategic drift where execution diverges from intent. All of these can potentially be gleaned from employee use of Praxis.

No. Strategic Radar reports findings: this bears on something your strategy depends on, and you may want to look. It doesn’t predict, recommend or rank. It isn’t a replacement for your own thinking or your consultant’s research — it’s an additional input. Reading a finding and setting it aside is a valid response. But so is considering it and doing deeper research or consulting a subject matter expert to look at a specific finding’s area more closely.

Diamond Mine surfaces conditions that already work in your favor but that your strategy isn’t using — such as demand in a new vertical, a structural advantage you could already leverage, or a competitor disadvantage you might exploit. It presents them as uncut diamonds: unranked and uncounted, because a fact about conditions has no strategic value until you decide to use it.

Diamond Mine is not strategy advice. It is an accounting of the openings already there to take. If you revise the strategy to use one, the schema updates — and a condition that was irrelevant to last year’s strategy can become the one that matters most under this year’s. But Diamond Mine may also find a condition that you deliberately decided not to exploit. Again, it only provides findings. You decide what (if anything) to do with them.

Strategic Radar tracks change: what is moving in the conditions your strategy depends on. Diamond Mine looks at what is already true: conditions in your favor that the strategy under-uses. Radar asks whether the ground is shifting; Diamond Mine asks what you’re standing on and not using.

Diamond Mine is only available once for each strategy. If you change the strategy in any way though, it becomes available again.

Look at the pattern rather than individual complaints. When many reps use Praxis to work through the same pricing pressure, Strategic Radar surfaces that pattern, anonymized, alongside outside signals such as competitor pricing moves. It reports the pattern and what it bears on. Whether the answer is pricing, positioning or capability is your call.

No single rep is reporting that the strategy is wrong; each is trying to close a deal. The strategic signal exists only in the aggregate. Team signals require at least 50 active users sustained over at least 90 days.

Because that isn’t how people think about their work. Nobody comes to a portal to talk about the strategy; they come with the problem in front of them. Individually those problems aren’t about strategy. Aggregated, they show where the strategy is meeting the market and where it isn’t — a request you deprioritized, or indifference to the thing you’re betting on.

Leaders have the opposite difficulty: they are invested in the strategy succeeding. A model scanning for change has no stake in any particular outcome.

Back to the strategy: renewal

You revise it in Contextuum, and the schema update propagates across the platform instantly. Everyone works from current thinking, including the scenarios people meet tomorrow. There is no retraining campaign and no need to rebuild the strategy from scratch.

A revision also changes what Diamond Mine and Strategic Radar look for, because they work from the current schema. Renewal doesn’t always mean change: sometimes a finding confirms the strategy, and it is renewed with the same conviction.

Strategy Iteration lets leaders update the strategy without starting over. It includes Team Strategy Review, for revisiting the team’s thought process; Individual Refresh, for anyone who missed the retreat; Strategic Calibration, for proposing changes and calibrating them against the rest; and Collaborative Strategy Creation, a remote, asynchronous retreat, coming soon.

Individual Refresh walks them through the thinking behind the strategy, not just the conclusions, and Team Strategy Review lets the whole leadership team revisit its reasoning together. They can then take the Strategy Introduction and use Praxis like everyone else.

Set up the strategy for successful activation. Upload the offsite’s documents to Contextuum and complete the set-up. That builds the schema. Have the strategy owner complete the Core Interview. Then, following your town hall or regular strategy roll out, invite your team members to Contextuum where they can generate their own Strategy Introductions. Once they pass the Introduction they gain access to Praxis.

While the team is encountering the Introductions, you can review the Findings Module and consider anything that Diamond Mine has provided. From there, Strategic Radar will regularly scan and bring evidence back. Changes you choose to make become Strategy Iterations, and update the schema and all other Contextuum functions.

The offsite is rarely the failure. The strategy it produces simply has no route into the decisions that follow, and no route back when conditions change.

Consultants and other audiences

Contextuum complements strategy consulting. A consultant can build a client’s schema from the engagement’s outputs and run everything except the Core Interview, which the client’s strategy owner must complete. Diamond Mine and Strategic Radar findings give consultants material for ongoing work after the engagement ends.

Collaborative Strategy Creation, coming soon, will let a consultant lead a remote, asynchronous strategy retreat inside the platform.

Team Strategy Review and Individual Refresh let a board member understand the reasoning behind the strategy — the alternatives considered and the trade-offs made — rather than only its conclusions. Right now, there is no role-based permission for Board members or Investors, but they can be added to the platform as Employees.

No. Activation, the schema, Diamond Mine and Strategic Radar’s environmental scanning work at any size. The one threshold is team signals into Strategic Radar, which begin at 50 active users sustained over at least 90 days, so that employee input can be meaningfully anonymized and aggregated.

Getting started and cost

Three ways. Quick Start takes about 30 minutes: answer six strategic questions about your organization, then experience the platform as any employee role. The Simulation lets you play one of 12 roles across 4 well-known companies in 5–10 minutes each. Or sign up for the full product and enter your own strategy.

Quick Start and the Simulation need no commitment and no credit card. The Simulation features real companies, with strategies inferred from publicly available information. Those companies are not clients.

Signing up is free, with no credit card: the strategy schema, the Strategy Introduction, Praxis and Strategy Iteration are all included. The Findings Module — Strategic Radar and Diamond Mine — is in early access, opened case by case on application.

Apply to the beta. Applications are reviewed individually, and selected organizations get the Findings Module, where both run. Because Strategic Radar and Diamond Mine work from your completed strategy setup, applicants must already have a Contextuum account and have completed the Core Interview. To apply, complete the access request form. A team member will respond with next steps.

None dedicated. Once the schema is built, employees take the Strategy Introduction and use Praxis on their own schedule, Strategic Radar runs on the schedule you set, and anyone with permission can update the strategy. There are no workshops to coordinate or facilitators to hire.

Not yet. Contextuum is currently standalone, which keeps setup free of IT work. Integration with existing tools, connecting strategic context to performance data, is coming.

Security and privacy

Your strategy stays yours. The schema and everything you upload remain your organization’s proprietary information, are not used to train AI models, and are not shared with other organizations.

Access is controlled at the database level. Row-level security confines every record to the user it belongs to and to those your organization’s admin has granted permission. Data is encrypted in transit and at rest, and we run regular security audits. If you have specific compliance requirements, tell us and we will work with you.

No. Each organization’s workspace is isolated. There is no shared space, no directory of customers, and no way for one organization to access another’s strategy. You decide who inside your organization can see or edit it.

Praxis conversations stay private to the person who wrote them. For Strategic Radar, employee input is anonymized and aggregated into patterns and themes — what kinds of customer signals, friction or drift are appearing — never attributed to individuals. The one thing leaders do see by name is Strategy Introduction progress: who has started, who has completed it, and each person’s alignment score. Praxis usage is not reported today; when it is, it will be an average number of daily users, never named individuals.

Not Ready to Try It Yet?

Stay updated on new features and strategic thinking resources.