The problem

If your risk discussions aren't changing what you do each week, all you have is a story.

Many risk registers are maintained rather than used. They get reviewed, they get a color, and the Weekly Schedule underneath them does not move. The register satisfies a process, and the blind spot sits exactly where it was.

The gap is rarely in the people. It is that the method lives in a two-day workshop and the work lives in a spreadsheet nobody opens between meetings. These instruments close that distance by making the method the thing you type into, so that a risk written on Tuesday has somewhere to go by the Weekly Accountability Meeting on Thursday.

What is in it
Open tools
No account. Nothing you type is stored.
CEI Work Session
Write a risk as Cause, Effect and Impact, and get coached until it is one. The coach will not rewrite your words for you.
Live About 10 minutes Open →
CEI Risk Coach Demo
See the coaching run on a worked example first, using a concern of the kind teams usually raise.
Live About 3 minutes Open →
The client environment
One workbench per project, for teams in an engagement. Sign in required.
Project Statement
The anchor document: the one-liner, the target customer, the measures of success, and the components that follow from them.
LivePer project
Risk Action Plan
Every risk in Cause, Effect and Impact form, with a priority, a singular owner, and proposed mitigations.
LivePer project
Cost of being late
The linear and nonlinear cost of missing the date, held against the project rather than in a slide somebody made once.
LivePer project
Who it is for

Project leaders and track leaders in a live commitment phase.

It assumes you are trying to make a credible commitment, not trying to report on one. If you own a track, if you have to bring your single top risk to the Weekly Accountability Meeting every week, or if you are the one person accountable for a result, the instruments are pointed at you.

It is not for an executive who wants a portfolio status roll-up. There is no such view, and adding one would quietly change what the team is willing to write down.

How it is deployed

Ordinary hosted software, described plainly.

The open tools run in your browser and need no account. The client environment is a hosted application: it runs on AWS Amplify, project data lives in a Supabase Postgres database with row-level security scoped to your workbench, and the text of a coaching request is sent to Anthropic's API to generate the response. That last point is the one worth knowing, because it means your words leave the application, and I would rather you heard it here than found it later.

The Workbench is a hosted service run by Celerity Consulting Group. Where the data sits, who can read it, what is logged, and what happens to a coaching request is set out on the security page.

Start with one real risk.

Not a sample, and not one you have already solved. Bring the thing you are hesitant to say out loud, because that is the one likeliest to be sitting in the team's blind spot.

Open the CEI Work Session Talk to me about your project