What's New Across Visual Decisions This Week (June 14, 2026)

valuemaps can now read a program's value the way you actually think about the business: by initiative, by use case, by company goal, and across the six CESMII dimensions, with every dollar still tracing to the P&L. Plus the whole funnel got smoother and opened up to outside partners.

Last week valuemaps grew up into a portfolio tool: bundle initiatives into a program, gate them on cost and time, and walk out with the procurement spec. The gate answers what is worth doing together. This week answers the next question: how do you read that value? Because the CFO, the plant manager, and the VP of strategy do not look at the same number the same way. The program report now lets each of them read the same CFO-validated value through the lens they actually think in, and follow any thread from a single use case all the way to the P&L line it moves. Alongside that, the whole surveys-to-use-cases-to-valuemaps funnel got noticeably smoother, the three sites now tell one consistent story, and outside consultants and partners can be brought in.

It was a big week. Here is the shape of it.

One value, read through whatever lens you think in

A program's value is one audited number, but no two people in the room read it the same way. A CFO reads it by P&L line. A plant manager reads it by the operational KPIs that move. A strategy lead reads it by company goal, or by where it lands across the manufacturing capability landscape. The program report now has a simple picker with two controls, an outcome and a dimension, and it re-expresses that same value accordingly:

Outcome: dollars (EBITDA), the operational KPIs that move (rolled up by SQDCI), or those same KPIs organized by your company's goals.
Dimension: by initiative, by use case, or across the six CESMII dimensions (manufacturing strategy and leadership, manufacturing excellence, data-driven processes, systems integration, workforce, and supply chain).

Pick any combination. The dollar views always reconcile back to the exact value the CFO signed off on, to the penny. The KPI views are an operational signal: grouped, compared, and never faked into a single dollar figure they are not.

A few things make it a report you can actually put in front of a leadership team:

A plain-language executive summary at the top, written straight from the numbers: the net value and payback, where the value concentrates, where it lands on the P&L, and how many initiatives clear the gate.
Drill in anywhere. Open a CESMII dimension to see the exact use cases inside it, where each one lands on the P&L, and the KPIs it moves. Open a use case and do the same. Every use case links back to its full write-up.
Investment, per dimension. Each row carries not just its value but its share of the investment and a simple payback, so a dimension reads as its own small business case rather than a number with no cost attached.
Follow the whole thread. New flow diagrams trace value from a single use case, up into the CESMII dimension it belongs to, through the initiative that delivers it, to the P&L section it moves. Where two initiatives share a use case, you can watch the flow narrow as the overlap is removed. That narrowing is the de-confliction made visible: shared work counted once, not twice.

The same CESMII breakdown is now available on an individual saved scenario, not just on programs.

The deeper point: this is one engine, not four separate reports bolted together. Your company goals and a full triple-bottom-line view become configurations on the same substrate, and every one of them is held to the same rule. It has to sum back to the validated total, or it does not ship. The brand has always been that every number traces. This keeps it true no matter which way you slice the value.

The funnel got smoother, and easier to find your way through

The path from a survey to a decision runs surveys, then use cases, then a saved list, then an initiative, then valuemaps. This week that path got a real cleanup so each stage has one clear job.

The list is for selecting; the initiative is where the deliverables live. Browsing and narrowing happen on the list. The moment you are ready to act, you save an initiative, and that is the single forward step into valuemaps. No more competing paths doing half the job each.
Both pages now show you where you are. The Lists and Initiatives pages carry your context (who owns what, and status), and initiatives are now attached to your company rather than floating on one person's account.
A capability footprint on every list, so you can see at a glance the shape of what a set of use cases actually requires.
Solutions are prioritized within the list page instead of arriving in an arbitrary order.
Save all at once. A "Save All" button on the use-case browser turns a whole filtered view into a list in one click.

Net effect: fewer dead ends, and the next step is always obvious.

Surveys: clearer questions, clearer progress

Every survey question now has a help pop-out. All 2,846 of them. Each one restates the question in plain shop-floor language, spells out the jargon and acronyms (KPIs, MES, Cpk, SPC, and the rest), and frames what low versus high maturity tends to look like, without ever telling you what to answer.
A clearer progress bar that is easier to see and advances with every question, so you always know how far you have left to go.

One consistent story across all three sites

The three sites increasingly tell a single story, so we made them look and move like it.

A high-level flowchart on each homepage that lays out the steps that happen on that site, so a first-time visitor can see the shape of the thing before diving in.
The ExampleCo worked example navigates the same way everywhere. The clickable workflow buttons that walk you through the demo, first built on valuemaps, now appear on the surveys and use-case demos too.
Matching look and language. The surveys ExampleCo page picked up the dark hero the other sites use, and the demo headers were rewritten for consistent wording end to end.

Teams, companies, and now outside partners

Manufacturing decisions are made by teams, and often with outside help, so the platform got more multi-player.

Bring in a consultant or partner. A new access model lets an outside advisor be granted read-only access across all three sites, with proper access controls. The consultant helping you choose a system can see the same picture you do, without taking it over.
Company-owned gap lists. The curated priority-gap list generated from your team's survey responses now belongs to the company, not just the admin who happened to click generate. Everyone in the company, and its plants, shares one list instead of each person minting a private copy.
Company admin, cleaned up and shared. In surveys, company administration is now separated from company reporting so the two jobs stop crowding each other, and the company-admin surface is common across the whole platform instead of rebuilt per site.
NAICS codes are now in the industry picker, so a company classifies itself the way the rest of the world does.

Behind the scenes

Programs and portfolios became one concept. We collapsed a redundant layer, so there is now a single clear "Programs" idea instead of two overlapping ones.
Consistent vocabulary. A terminology sweep aligned naming across the platform (the requirements document is now consistently the URS, and Archetype is now Solution). Display only, so the words on screen match the words people actually say.

Coming soon

The lens engine is built to be extended. The next lenses riding on it are your company's goals as a first-class view in the deliverables, and a CESMII coverage and gap view that calls out where your roadmap is heavy and where it is thin. Both are configurations on the substrate that shipped this week, not new builds.

Questions, feedback, or want to read your own program's value through your CFO's lens and your plant manager's at the same time? Reply to this email, or hit the Feedback button on any of the three sites. We read everything.

— Tim Stuart, Visual Decisions