Since our last update on April 29, we’ve been heads-down on a question every product and portfolio leader eventually asks: “Great, the team is shipping — but are we shipping the right things, and who decided that?”

Eleven weeks. The answer is now three new pillars — Decision Center, Value Stream Operations, and Unified Planning — plus a Technical Debt dashboard that finally puts a number on the debt everyone already knew was there. Here’s what changed.

🧭 Decision Center — New Domain

Every organization runs on decisions — capital allocation, build-vs-buy, schedule tradeoffs — but most of them live in someone’s inbox or a slide nobody re-opens. Decision Center gives every decision a lifecycle: Draft → Framing → Evaluating → Ready → Decided, visible org-wide in a Kanban, list, or map view. Open any decision and you get a structured A3 report (goal, problem, root cause, countermeasures), weighted options scoring against evaluation criteria, ROAM risk tracking, AI-generated option suggestions, stakeholder voting and consultation, and a post-decision follow-up loop. We even bridged Andon escalations straight into Decision Center, so a blocked team’s “we’re stuck” signal becomes a framed decision instead of a stalled thread.

📡 Value Stream Operations — New Command Layer

Flow metrics are only useful if someone actually looks at them before things go sideways. The new Operations Radar answers one question — “Where should leadership intervene this week?” — by rolling up flow velocity, flow time, flow efficiency, and WIP across every value stream into a single triage view, complete with data-freshness indicators so you know exactly how current the signal is. Drill into any stream and the new Flow Map renders every activity as a node you can click into, surfacing cycle time, WIP, and defect share per step — so “settlement is slow” becomes “ledger writes at the Settlement node are the bottleneck.”

🧩 Unified Planning — Strategy to Outcomes

This is the connective tissue that was missing between strategy decks and sprint boards. The new Planning workspace walks every objective through five stages — Story (Direction, Choices, Value journey, Commitments, Proof), Define, Align, Plan, and Review — with cascading commitments by audience (Executive brief, Leader cascade, Team impact) so the same objective reads differently depending on who’s looking. The Align tab’s traceability map is the payoff: a single canvas connecting the portfolio objective down through tactics, metrics with confidence scores, and the value streams and work items actually driving each number.

🔁 Portfolio Steering — Closing the Loop

Planning is only half the story — someone has to check whether the plan happened. Portfolio Steering compares a published baseline against reality: objectives on track, financial variance against actual spend, value delivered per stream, and delivery completion, broken down stream-by-stream with planned cost vs. delivered vs. value variance. It ships with an auditable review trail and a reallocation workflow, so when a stream is $9M under-delivered against plan, that’s not a Slack message — it’s a governed decision with a paper trail.

🛠 Technical Debt Dashboard — New Domain

Ships this week: a consolidated view of debt your teams already know exists but leadership never sees in one place. It pulls together technical-debt defects, maintenance/debt-tagged backlog share, technology version deviations (we’re looking at you, .NET, Node.js, and PostgreSQL), capability-debt findings, and open technical impediments — with trend lines so “we have some debt” becomes “1.9% of the backlog, five technologies drifting, three findings this month.”

🔧 Also in This Release

• AI-generated storyboard mockups — Turn a scene description into a real image with OpenAI-backed mockup generation, plus scene-to-work-item suggestions straight from the storyboard
• Multilingual storyboards — Full i18n support (English/French) with localized duplication, so global stakeholders review in their own language
• Decision Center Performance analytics — Org-level decision throughput and cycle-time analytics, not just individual decision records
• WSJF scoring fix — Corrected an edge case that inflated WSJF when job size sat at the minimum Fibonacci value
• Capability scan proposal review — AI-detected capability changes now go through a trackability-evaluated review step before they land

Decision-making, flow health, strategic traceability, and technical debt all used to live in separate spreadsheets, decks, and tribal knowledge. Now they’re one product, one source of truth.

Where does your organization’s decision trail break down — before the decision, or after it?👇

Curious about Dretza Stream Central? Give it a try at https://streamcentral.dretza.com