Skip to content

v0.26.0

Release Date: 2026-11-12

Highlights

  • The Balanced Scorecard joins OKR, V2MOM, VSEM, and OGSM in goals. goals/bsc models a scorecard as strategic objectives in perspectives, linked cause to effect in a strategy map, with lead and lag measures and the initiatives that close the gaps. It comes with validation presets, Markdown and Marp renderers, a generated JSON Schema, and a splan goals bsc command.
  • Every goal framework's Markdown can sit inside a larger document. OmitHeader leaves out a document's title, and HeadingOffset moves its headings down, for the VSEM, OGSM, MEL, DMAIC, and Balanced Scorecard renderers. DMAIC gains a portable Markdown renderer.

Overview

A Balanced Scorecard describes a strategy as objectives in a few perspectives, balanced so that the results an organization reports are not pursued at the expense of what produces them. The four classic perspectives are financial, customer, internal process, and learning and growth; they may be renamed, reordered, or replaced, and a public agency or nonprofit often puts a mission perspective on top. Lead measures say early whether the strategy is working; lag measures say whether it worked. See the Balanced Scorecard guide.

A tool that builds one document from several plans, such as a theory of change followed by a VSEM and a MEL plan, can now place each renderer's output under a heading of its own. With OmitHeader and a HeadingOffset of 1, a plan's level-two sections become level three, under the caller's level-two heading. See Embedding rendered plans.

Changes

goals/bsc

  • BSC, Metadata, Perspective, Theme, Objective, Measure, Thresholds, and Initiative, with New, ReadFile, Parse, and WriteFile. New and DefaultPerspectives give the four classic perspectives, top first; each perspective's kind says which classic role it plays, whatever it is called.
  • Objectives name their perspective and their strategic themes, and link cause to effect with contributesTo. Measures name their objective, are lead or lag, and carry a baseline, a target, and thresholds at which they turn green or red. Initiatives name the objectives they serve. ObjectivesIn, ObjectivesInTheme, ContributorsTo, MeasuresFor, and InitiativesFor read the scorecard.
  • Cascading: metadata.parentId names the scorecard a team's scorecard cascades from.
  • Validate with two presets. Structural problems are always errors, including a cycle in the strategy map; a link that runs down the perspectives is a warning. Missing targets, owners, measure types, measures, strategy-map links, and a lead or lag measure on each objective are warnings under DefaultValidationOptions and errors under StrictValidationOptions.
  • Renderers in goals/bsc/render/markdown (with the strategy map as a Mermaid diagram) and goals/bsc/render/marp (slides, with the strategy map as a table). Both produce the same bytes for the same scorecard.

goals

goals.FrameworkBSC, goals.NewBSC, and Goals.IsBSC add the Balanced Scorecard to the union. A scorecard's objectives are its goal items, tagged with their perspective, and its measures its result items, labelled "Objectives" and "Measures".

Embedding the Markdown renderers

  • OmitHeader and HeadingOffset on the render Options of goals/vsem, goals/ogsm, goals/mel, goals/dmaic, and goals/bsc.
  • OmitHeader leaves out the title and the metadata line under it. HeadingOffset pushes every heading down that many levels, capped at level 6, and leaves fenced code blocks, such as Mermaid diagrams, alone.
  • Only the Markdown renderers read them; the Marp and Pandoc renderers ignore them. Both default to off, and the output with the defaults is unchanged.

goals/dmaic

goals/dmaic/render/markdown writes a DMAIC document as portable Markdown, with no front matter, LaTeX, or page breaks: an overview with health by category, a metrics table for each category, and detail for each metric that needs attention. The phase distribution, root causes, initiatives, and process capability metrics follow when their options are on. The output is deterministic.

splan

  • splan goals bsc has validate (with --strict), generate markdown, generate marp (with --theme), and init. The template meets the strict options.
  • splan goals validate detects a scorecard from its perspectives, and splan goals init --framework and splan schema generate --type accept bsc.
  • splan goals dmaic generate markdown writes the new DMAIC format, beside marp and pandoc.

Schema

schema/bsc.schema.json is generated from the Balanced Scorecard types and embedded as schema.BSCSchema() and schema.BSCSchemaBytes(). The PRD schema is regenerated because it embeds the goals union, which now has a bsc option.

Examples

examples/minimal.bsc.json and examples/product.bsc.json, a fictional bookkeeping app's scorecard with two strategic themes, are checked to validate. The full example also meets the strict options.

Documentation

  • A Balanced Scorecard guide covering perspectives, the strategy map, lead and lag measures, cascading, how it differs from OGSM and VSEM, validation, goals alignment, rendering, and the command line.
  • The goals overview sorts the frameworks into strategy plans, improvement plans, and measurement and learning plans, gives each framework's origin, and explains how to embed rendered plans in a larger document.
  • The DMAIC guide covers the Markdown renderer, and the VSEM, OGSM, MEL, DMAIC, and Balanced Scorecard guides explain the embedding options.
  • The Balanced Scorecard in the README, the documentation home, the API reference, and the getting-started pages.

Compatibility

Additive only. An API comparison against v0.25.0 reports the new goals, schema, and cli identifiers, the new render options, and the new packages as compatible changes, and no incompatible changes. JSON written by v0.25.0 reads unchanged, and Markdown output with the default options is byte-identical to v0.25.0.

Installation

go get github.com/grokify/prism-roadmap@v0.26.0