Component library

Showing 2 components with role statement.

Narrative

<KeyFinding>

workshopStatementContentNarrative

Highlighted observation from the engagement, with severity colour-coding.

When to use: Call out an insight that materially affects the client's decisions. A 12-page report typically has 4–8 of these.

Preview

Key findingHigh impact

Order intake passes through five inboxes before reaching ERP

Every customer order today is touched by sales, customer service, operations, finance, and operations again. Each handover is a manual email or shared inbox forward.

Prop	Type	Notes
severity	"low" \| "medium" \| "high"	Optional. Default: `medium`. Visual emphasis. High = red ring, medium = amber, low = neutral.Values: low, medium, highExample: `high`
title	string	Optional. Optional title shown above the body.Example: `Order intake passes through five inboxes`
children	ReactNode	Required. The finding's body prose.

Examples

<KeyFinding severity="high" title="Order intake passes through five inboxes before reaching ERP">
    Every customer order today is touched by sales, customer service,
    operations, finance, and operations again. Each handover is a manual
    email or shared inbox forward.
</KeyFinding>

<Callout>

sharedContentStatementNarrative

Generic emphasis box for asides, important context, or warnings.

When to use: Use when text needs visual separation from surrounding prose but isn't a finding or recommendation. Common: 'assumptions to validate', 'what we mean by X', 'next steps'.

Preview

Prop	Type	Notes
tone	"info" \| "success" \| "warning" \| "danger"	Optional. Default: `info`. Colour and icon.Values: info, success, warning, dangerExample: `warning`
title	string	Optional. Optional headline.Example: `Two assumptions to validate in week 1`
children	ReactNode	Required. Callout body.

Examples

<Callout tone="warning" title="Two assumptions to validate in week 1">
    The projection above assumes the ERP middleware can be exposed within
    the first three weeks, and that the AP team is willing to triage
    exceptions in a Lunnoa queue rather than email.
</Callout>