Diagram templates

Explain three to eight parts or features of one product, device, document, organism or concept.

Explain a brief, proposal, policy or report with 3–5 ordered sections.

Contract section review, onboarding guide explanation and product brief review.

For explaining what one thing is made of as a primary part, the part that carries it out and a part that spans both: a service offer (scope, delivery, assurance), a product (core function, how it ships, support), a course (content, format, learner support), an event (program, logistics, hosting) or a team charter (mission, ways of working, backing).

A C4 system context diagram, a "who uses it and what it depends on" slide, or an integration overview: one system, one to four actors that use it, and one to five external systems it calls or that call it, each link saying what it does.

Three to twelve components that call or depend on each other with no fixed tiers, such as a microservice call map, a service dependency graph, or data lineage between systems, with links labeled by protocol or what flows (gRPC, REST, events).

One system shown as two to four copies that are compared side by side: dev, staging, and production environments with promotion between them, region A, region B, and disaster recovery with replication, or blue and green stacks.

Event flows through one broker, bus, or topic hub with one to five producers and one to five consumers, such as Kafka topics, Google Pub/Sub, SNS fanning out to SQS queues, EventBridge rules, or a webhook gateway delivering to several handlers; built for fan-in and fan-out.

Two to fourteen components placed in two to five networks, clusters, subnets, or accounts, such as an AWS VPC with public and private subnets or a Kubernetes cluster with namespaces, optionally inside one region with users or third-party services outside.

A layered system where components rely on specific components in the layer directly below: software layers from experience through services to data, an operating model from strategy through operations to delivery teams, or a data stack from reports through warehouse and pipelines to sources.

Two to four tiers, environments or network zones that a request or data flow crosses in order, each holding one to three services: a cloud web stack from edge to data, an IoT path from devices through gateways to analytics, a payments flow from channels through processing to ledgers.

A system of two to sixteen components arranged in two to five layers, such as a web app's stack or a SaaS platform from clients through edge and services to data, with calls between neighboring layers.

Two to fourteen components inside containers that hold other containers, such as an AWS account with a VPC and its subnets, a GCP project with a VPC, or a Kubernetes cluster with its namespaces.

Data moving through two to five stages of tools, such as an analytics stack, an ETL or ELT pipeline, event streaming, or an ML feature pipeline, with two to fifteen tools and labeled flows between neighboring stages.

Three to eight hops of one request in order, such as a request through CDN, gateway, services, and database, an auth or checkout request trace, or a webhook delivery path, optionally with the protocol or measured time of each link.

Security reviews, threat-model data-flow diagrams at the zone level, and network segmentation: two to five zones from least to most trusted (such as internet, DMZ, internal network, restricted data) with two to fourteen components and the control on each crossing (WAF, mTLS, API key, VPN, firewall rule).

Compare two or three options across three to six attributes that can be scored or rated low, medium, or high, such as cost, speed, and effort.

Compare three to ten amounts of the same kind, such as sales by region, survey answers, or time per task.

Actual-versus-target values sharing one nonnegative scale and explicitly supplied range boundaries.

A schedule laid out by period and time slot, such as a week timetable, a conference day plan, a content calendar by week, or a weekly meal or workout plan, with events that occupy one or more consecutive slots.

Three to nine parallel features, benefits, capabilities, or values of one product, service, or team.

Suits a market or vendor landscape, a partner or integration ecosystem, an investment portfolio by sector, a tool stack by function, or suppliers by capability: who belongs where, at a glance, with real logos.

Parallel principles or takeaways.

Supplied team members, speakers, advisors or project participants.

Parallel services, offerings, practice areas or modules with explicit included points.

Two to eight parallel features, benefits, services, use cases, or principles that each need a sentence or two of explanation.

Suits explaining the turns in one measure over time: monthly active users with launches and outages, revenue with pricing changes, support volume with policy changes, website traffic with campaigns, headcount with reorganisations.

Show how much pairs of participants share, and who is most connected, when order along a line helps: joint projects between teams, referrals between channels, cross-sell between products, trade between regions, co-authorship between groups.

Compare 1–4 complete nonnegative series over 3–10 supplied equally spaced ordered categories as overlapping filled areas from zero, with point and line boundaries.

Place one subject against a peer group's spread on two to eight metrics with different units: company or product benchmarks, a store or region against its network, salary or offer positioning against a market survey, a team or school against its organization.

Show how one additive measure spreads across two lists when the pattern of large and small amounts matters more than exact shades, such as leads by channel and month, feature usage by customer segment, skills by team, or orders by store and weekday.

Show how groups acquired at different times keep contributing to one additive total: revenue by customer cohort, active users by signup year, donations by donor cohort, or orders by first-purchase quarter.

One measure over ordered categories such as months, quarters, versions or stages, or for amounts that can go negative, such as profit by quarter.

Two complete nonnegative marginal breakdowns of one positive common-unit total: funding sources and uses, staffing hours and work allocations, or energy supply and end uses.

Suits supply curves (mines, plants or suppliers by capacity and unit cost against a market price), marginal abatement curves (measures by potential and cost per unit, with negative costs as savings, against a carbon price), and sourcing or procurement curves (suppliers by volume and price against a budget ceiling).

A positive common-unit allocation with two to four parts and an exact complete two-to-four-part breakdown of one selected parent.

For complete supplied counts on one five-class ordered scale compared across two or three groups: survey agreement by segment, review star ratings by product, risk ratings by business unit, performance grades by team or difficulty ratings by release.

One whole whose single part needs its own composition: revenue by region with one region by country, a budget with one department by line item, traffic by channel with paid split by network, time spent with meetings broken down.

One meaningful whole split into two to six supplied positive amounts in one common unit, or a complete percentage distribution, such as a budget by category, revenue by source or traffic by channel.

Compare 2–8 paired signed finite before and after amounts as linked vertical points on one common axis.

For program attendance, licensed accounts or project staffing expressed as small exact counts.

Suits a supplied outlook continuing a measured history: revenue or bookings scenarios, headcount or demand plans, cost projections, user growth targets and capacity forecasts.

Show a supplied finite value on an explicitly bounded semicircular scale.

A countable whole of ten to two hundred units split into two to eight groups, where reading the blocks against each other and against a threshold matters: a board or council vote against a majority, committee or panel composition, a workforce by role, survey responses by answer, customers by plan.

The trend of one nonnegative measure for up to three series over four to ten equally spaced periods when a solid presentation look suits the slide, such as monthly recurring revenue by plan, active users by platform over quarters, pipeline value by region over weeks or support tickets by channel over months.

Acquisition channels by cost and conversion with spend, stores by traffic and sales with staffing, or products by growth and margin with revenue.

Independent launch workstreams, fundraising targets, training completion or sustainability commitments.

Two observations of one comparable nonnegative quantity across a few categories: handling times, customer counts or planned and actual units.

One whole built up from two to seven ordered parts in one common unit, where the stacking order means something: a price built up from cost, margin and tax, the cost of a product from materials to shipping, the time budget of a process from intake to delivery, a revenue build from base to expansion, or a complete percentage breakdown in a meaningful order.

One meaningful whole split into two to six supplied positive amounts in one common unit, or a complete percentage distribution, when a solid presentation look suits the slide, such as revenue mix by product, budget allocation, traffic sources or market share.

Several measures each tracked against its own target, compared by the share reached: sales quota attainment by region or rep, fundraising toward campaign goals, OKR key results, migration or rollout completion, hiring against plan.

Supplied fulfillment-time, order-value or employee-tenure distributions with contiguous equal-width intervals and nonnegative whole counts.

Compare two or three complete percentage compositions with two or three shared parts, such as regional revenue mix, budget allocation or workforce mix.

Compare two nonnegative series of one unit category by category, such as this year against last year by product, two regions by sales channel, two customer segments by survey answer or two teams by ticket type, when a solid presentation look suits the slide.

Explain the exact monetary change when both a positive unit price and a positive whole-unit quantity increase: ticket revenue, room revenue or purchasing cost.

One nonnegative measure across categories, optionally clustered into two to four groups, such as revenue by region and quarter, units sold by store and month, survey responses by segment or headcount by team, when a solid presentation look suits the slide.

One nonnegative measure broken down by two short lists, when a solid presentation look suits the slide, such as revenue by region and quarter, cloud spend by team and month, tickets by channel and weekday, orders by store and product line or headcount by office and function.

One positive measure across independent peers whose amounts span a wide range, where columns would flatten the small ones: market size by segment, revenue by country, users by platform, spend by department, deal value by account.

One signed measure across categories in supplied order, such as budget variance by department, monthly net cash flow, year-over-year change by region or profit and loss by product line, when a solid presentation look suits the slide.

One nonnegative measure across a repeating cycle when the shape of the whole cycle matters and a solid presentation look suits the slide: monthly bookings or sales, footfall by hour band, support tickets or orders by weekday.

A single bounded measure with an explicit target: quota attainment, project completion or capacity use.

Mutually exclusive additive components of one common quantity across equally spaced supplied periods.

Two to four additive parts of one nonnegative measure across three to eight categories, such as revenue by region split by product line, headcount by department split by level, support tickets by month split by channel or spend by quarter split by cost type, when a solid presentation look suits the slide.

One measured quantity moving through a chain of stages where every middle station passes on exactly what it receives: supply chain volumes from suppliers through plants to stores, data moving between systems in a pipeline, students moving from intake routes through programmes into destinations.

Show how one whole divides into groups and parts at once with a solid presentation look: a portfolio by asset class and holding, revenue by region and product, an operating budget by department and program, or headcount by function and team.

Acquisition mix, service demand or a budget composition across two supplied groups or periods.

Compare small whole-number counts of discrete things across categories, where one item is one countable unit, such as new hires by team, deals signed by channel, stores by region, open roles by department or incidents by service.

Complete mutually exclusive compositions supplied as whole percentages: single-choice survey responses, budget allocation or product sales mix.

For a bridge from an opening to a closing total through two to six ordered signed changes, such as cash, revenue, headcount or budget, when a solid presentation look suits the slide.

Compare 1–4 complete series over 3–10 supplied equally spaced ordered categories with points and straight line segments.

Compact, low-ink comparison of 3–10 signed, positive, or zero numeric observations across named categories on a single quantitative scale.

Suits a two-way breakdown of one additive total: market share by segment and competitor, revenue by region and product line, headcount by department and level, budget by program and cost type.

Suits nested sizes of one quantity where each level is a subset of the one below it, when a solid presentation look suits the slide: total, serviceable and obtainable market (TAM, SAM, SOM), addressable users narrowing to reachable and converted users, a sales universe narrowing to qualified pipeline, or a total budget narrowing to allocated and spent.

Suits nested sizes of one quantity where each level is a subset of the one before: total, serviceable and obtainable market (TAM, SAM, SOM), addressable users narrowing to a target segment, a sales universe narrowing to qualified pipeline, or a budget envelope narrowing to committed spend.

For regional channel demand, workforce profiles or measured feature comparisons.

Programme objectives, audience coverage and training milestones.

A Net Promoter Score survey supplied as response counts per score: customer NPS, employee eNPS, post-support or post-purchase surveys, product or feature NPS.

Revenue mix, service demand mix and budget composition.

Compare 2–8 supplied actual amounts with corresponding targets on one common zero scale.

Show 2–6 positive supplied finite amounts as solid pie slices with a keyed side legend.

For two to five categories of one comparable quantity and unit compared against a plan: budget against spend, staffing plan against headcount, stock orders against receipts, study hours planned against logged, or sales targets against results.

Suits competitive price ladders and lineup comparisons: laptops or phones across brands, SaaS plans across vendors, agency packages, insurance tiers across providers, or one product's price across retail channels.

Compare four programme participation counts, service request categories or event session totals.

Three named options ranked first, second and third across three explicit reviews: supplier preference, product popularity or survey priorities.

One measure across a cycle of periods or a small set of peer categories, when the shape of the whole pattern matters: monthly sales seasonality, support requests by hour band, weekday footfall, spending by category.

A total and its make-up both change around a cycle: incidents by cause per month, support tickets by channel per month, energy use by source per month, visitors by type per weekday.

Show how two measures relate across many observations and how each one is distributed, such as deal size against days to close by segment, delivery time against distance by region, customer tenure against monthly spend by plan, or response time against satisfaction score by channel.

Compare how several groups split into the same parts, such as channel mix by region, spend mix by department, device mix by year, or headcount mix by office.

Suits comparing the shape of one measure across many segments at once: sales growth by region, sign-ups by channel, churn by plan, traffic by market, utilization by site, each optionally against an overall average or plan.

Compare 2–4 additive nonnegative series over 2–6 distinct supplied categories as horizontal stacked bars.

Suits growth stories told in consulting and investor decks: market size by segment over years, revenue by product line, active users by region, cloud spend by category, installed capacity by technology.

Compare 2–4 additive nonnegative series over 2–6 distinct supplied categories as vertical stacked columns.

Suits how a whole divides over time: market or browser share by year, revenue mix by product line per quarter, traffic by channel per month, workforce by region over years, energy mix by source.

Show one whole divided into groups and their parts at once: revenue by region and country, a budget by department and line item, headcount by function and team, or traffic by channel and source.

For two to five named identities with explicit integer ranks from one to six at three supplied reviews: supplier shortlists, league or poll standings, candidate evaluations, feature priorities or product rankings.

For an explicitly closed conserved cohort classified into two categories at each of three ordered stages, with all eight adjacent pair counts including known zeros: enquiries by origin, route and offer; students by entry track, course and outcome; patients by referral, pathway and setting; or orders by channel, warehouse and carrier.

Show one measure across places whose rough arrangement matters, such as customers per million by US state, sales by European country, or incidents by office floor and zone, when every place should be equally visible regardless of its real size.

A one-at-a-time sensitivity analysis of four to ten inputs against one outcome: a business case's net present value, a project's finish date, a price scenario's margin, a forecast's revenue, a budget's total cost.

Show how one whole divides into groups and parts at once: an operating budget by department and line item, revenue by region and product, headcount by function and team, or a portfolio by asset class and holding.

Show one supplied measure over 3–10 equally spaced ordered observations.

Suits strategy canvases and offer positioning: a new product against incumbents, service tiers against competitors, a proposed operating model against today's, vendors on buying criteria, or locations on visitor experience.

Show how one supplied finite signed opening value and 1–8 ordered changes produce a closing total.

Tasks to check or confirm.

Show exactly two competing considerations on a level balance scale.

For weighing two options or positions by scored reasons, such as pros against cons, build against buy, benefits against risks, or two vendors, hires or locations, when each reason carries a 1-5 importance weight.

Compare central and local responsibilities, paired service-tier roles or two learning perspectives at the same ordered levels.

A customer-base reconciliation, a staffing change or a portfolio update with explicitly classified retained, removed and added whole counts.

For comparing service offers, policies or working methods by the same criteria.

For paired support and ownership roles, training perspectives or current and future responsibilities.

Compare service formats, travel arrangements or membership offers on two to five qualitative criteria.

For proposals explaining which specific change connects each current condition to its proposed counterpart: a business process redesign, a product onboarding fix, a policy or classroom routine change, a team operating model, or a personal workflow.

Role-title migration, terminology replacement and offer repositioning.

For two to four supplied principles, each owning one exact preferred example and one exact example to avoid: brand voice guides, product interface copy, support reply standards, documentation style, naming conventions, inclusive language or meeting etiquette.

Compare two service formats, policy choices or working methods on two to five qualitative criteria.

For a compact qualitative causal-loop view with exactly five variables and two three-link loops sharing one variable: a referral loop against crowding in a membership plan, workload against hiring in a team, adoption against support load in a product, or demand against price in a market.

Three-phase improvement rhythms, creative iteration or learning cycles.

One ordered four-stage process repeating through two phases, two stages per phase.

Three to six phases that repeat in a loop, such as plan-do-check-act, a software or product lifecycle, a customer or sales cycle, or a data lifecycle.

For service setup and delivery, customer activation and use, or community onboarding and participation.

Three to five forces that reinforce each other around one outcome, such as a growth, marketplace, content, or community flywheel.

Six-phase campaign planning, product improvement or recurring operations.

Two phases that feed each other forever, each with two to four stages, such as DevOps (dev and ops), build and learn, design and deliver, or train and deploy.

For a recurring plan-do-check-act routine, editorial cycle or customer renewal cycle.

For a recurring process of four to six stages, such as a delivery, feedback or improvement loop, where each stage hands over to the next and the last returns to the first.

A material reuse cycle with new supply and disposal, reusable content with incoming briefs and retired material, or equipment use with acquisition and retirement.

For a loop of three to six stages that repeats, such as plan-do-check-act, build-measure-learn, a sales or account cycle, quarterly planning, or a release or content cycle.

Three to eight steps that repeat in a loop and need a sentence or two each, such as an operating rhythm, a sprint or release cycle, an incident management loop, or a budgeting cycle.

Recurring service improvement, programme review and publication cycles.

Delivery and discovery routines, customer and service improvement loops, or sales and renewal routines with an explicitly shared review stage.

For four-step recurring loops where each step produces one named output: service improvement, editorial planning, quarterly operating reviews, product discovery or a study-practice-test-reflect learning cycle.

Three to eight stages that repeat in a loop, such as a product or customer lifecycle, a plan-do-check-act loop, a release cycle, or a feedback loop.

A loop of three to six stages that is run two to four times, each pass reaching further: product releases that repeat a build-and-learn loop at a growing scale, a curriculum that revisits the same skills at a deeper level, an account expansion that repeats the same sales motion, a research programme that reruns the same study design with larger samples.

For planning rhythms, service improvement or editorial operating cycles.

For 3–5 stage recurring loops with named owners, produced work and an explicit final-to-first feedback artifact: customer learning loops, hiring or onboarding routines, editorial cycles, release reviews and continuous-improvement rounds.

Aligned customer and delivery routines, planning and execution reviews or supplier and store replenishment.

One to four questions with two or three answers each that lead to two to six outcomes over up to four levels, such as choosing a plan, approving a request, triaging a ticket, or picking a tool.

Dense binary dependencies including cycles and reciprocal edges.

Prescriptive guidance with 2–6 actions per side.

Compare the same measure on two sides for several items, such as before and after, last year and this year, or actual and target, where the gap per item matters, such as page speed by flow before and after a release.

A data model, such as the tables of a shop, a booking system, or a school database, where each entity lists its fields and each relationship states how many relate to how many.

A flat relationship with two to four named terms and a result, such as opening stock plus returns minus loans equals closing stock, or campaign spend divided by leads equals cost per lead.

Compare two to four plans, products, or tools feature by feature, with three to twelve rows in up to four labelled groups, and optionally one recommended option.

Organize supplied or explicitly brainstormed possible causes of one problem or outcome, such as late deliveries or a recurring defect, with two to six categories and zero to four causes per category.

A forward process with one or two binary decisions and short side branches.

A compact departmental handoff workflow for order fulfillment, employee onboarding or invoice processing.

Service-intake checks, programme eligibility or hiring qualification where every ordered condition must pass.

A forward process handed between two to four people, teams or systems, with three to ten steps and up to two decisions.

A forward-moving process of four to twelve steps with one to three yes/no decisions, such as an order approval, a support triage, a signup check, or a refund policy.

One straight sequence of three to eight steps where some steps need a side remark, such as a setup guide with tips, an onboarding flow with warnings, a data migration with caveats, or a release checklist with reminders.

Place a product, technology, internal tool, policy, practice or service on the diffusion of innovations curve: go-to-market planning for a B2B product, rollout of a new internal platform, adoption of a public-health practice, or spread of a teaching method.

For a product, service or retail offer’s proposed growth choices using explicitly classified initiatives.

Suits an enterprise or business capability map graded by maturity, an investment heat map (divest, maintain, invest), a function-by-function readiness or risk rating, or a service catalog marked by coverage: what the organization does, grouped by domain, and how each capability rates.

For morphological exploration of explicitly selected combinations: an event format combining audience, experience and delivery; a meal concept combining base, flavor and service; or a training offer combining cohort, format and pace.

For two to four supplied trait pairs with explicitly chosen qualitative positions for one subject: a brand personality, a team's working style, a product's design principles, a leadership stance or a service's character.

For sorting supplied situations, incidents, decisions or kinds of work by how cause and effect relate, so a team agrees how to respond: incident triage, strategy choices, portfolio or project work types, leadership coaching.

For program plans, career development or partnership design.

For a Design Council Double Diamond view of one discovery effort: a booking experience, public service, classroom activity or product proposition.

For project retrospectives, service reviews or personal working practices.

A product proposal examined through four perspectives, community priorities or the principles behind an offer.

Capabilities around a core offer, skills around a team's purpose, services around a platform or workstreams around a programme goal, where which parts sit next to each other matters.

Suits adoption assessments of emerging technologies, product categories, management practices, marketing channels or consumer trends, where each entry is placed in a hype-cycle stage.

For a compact qualitative Five Forces industry discussion using explicitly classified source factors.

Product review, venue choice and service policy.

Community service coordination, learning partnerships or distribution relationships.

For operating capabilities, partnership contributions or service ingredients assembled into one whole.

A familiar strategy house: business priorities supporting a goal, a school's ethos, or a public-service charter built on shared principles.

Suits classifying product features, service attributes, onboarding steps, store amenities or benefits by how their presence affects satisfaction, for product, service and customer-experience reviews.

Product stewardship, membership programmes and event attention cycles.

A selective Teresa Torres opportunity solution tree: one desired outcome, two supplied customer needs or pain points, one or two explored solutions per opportunity, and one named assumption test per solution.

Offer demand and supply, decision benefits and costs, or programme enablers and outcomes.

For partnership maps, stakeholder relations or cross-functional dependencies.

Market entry, workforce planning and community programme context.

Service contributions, shared programme principles or brand promises.

One overarching goal, vision, or mission held up by two to five parallel pillars (priorities, principles, capabilities, workstreams) on a shared foundation of values or enablers.

Show 2–5 distinct peer pillars as equal segments of a semicircle around one shared foundation.

Offer design with demand and delivery; Programme inputs and outcomes; Partnership contribution and support.

For sorting six to twenty named items into four categories and three or four ordered commitment levels: technology radars (adopt, trial, assess, hold), vendor and tool shortlists, initiative portfolios by readiness, market or channel bets by commitment, and practices by maturity.

For one supplied choice among three or four considered options with a single statement about the selected one: a target audience and its positioning, a pilot region and why it goes first, a shortlisted vendor and the deciding reason, or a chosen scenario and its premise.

For a compact qualitative bow-tie discussion of operational risks such as event crowding, supply interruption or missed service commitments.

For reviewing an organization against the seven fixed 7S elements with one finding each: post-merger integration, transformation readiness, operating-model diagnostics, change-program assessments, or a team health check.

A shared platform with delivery routes, a campaign with distinct outputs or one programme with several contributions.

For one shared basis adapted per branch: an offer tailored to audiences with their channels, a platform packaged into tiers with their prices, a policy applied per region with its owner, or a curriculum adapted per cohort with its format.

For theories of change, product or growth hypotheses, onboarding and engagement plans, policy or programme logic and process improvement proposals that explain which supplied assumption must hold for each step from one state to the next.

For a selective proposed strategy map using the standard four business perspectives and explicitly supplied adjacent-perspective influence hypotheses.

Service principles, programme contributions or product foundations.

Balance a portfolio across today's core, emerging and future opportunities: a bank's or retailer's growth strategy, an R&D or product portfolio, a public agency's modernization program, or a university's research agenda.

Three interdependent principles, project constraints, or dimensions around a shared subject, such as people-process-technology or desirability-feasibility-viability.

Three mutually connected partners, disciplines or service roles.

For three peer perspectives on one subject: desirability, feasibility and viability of an idea; people, process and technology of a change; customer, team and business views of a service.

Strategy rollout, school policy implementation and regional service standards.

For a qualitative sequence that first selects or focuses, crosses a shared decision or commitment, then broadens its activity or reach.

One-time qualification into continuing customer, employee or member activity.

Three to five qualitative narrowing stages in enrolment, recruitment or sales.

A sales, conversion, hiring, or filtering funnel with three to six stages.

Three to five qualitative narrowing stages in enrolment, recruitment or sales.

A checkout, recruitment or activation cohort with supplied non-increasing counts.

Three to six narrowing stages in sales, checkout, hiring, or filtering.

Four qualitative stages for workshop enrolment, recruitment or sales.

For staged decisions with explicit gates between adjacent stages: buyer journeys, hiring pipelines, grant or admissions review, product idea screening, vendor selection.

A compact overview of ordered narrowing stages: sales, hiring or idea screening.

Four qualitative buying, recruiting or investment-screening stages.

For conversion funnels with supplied whole counts per stage: sales pipelines, sign-up and checkout journeys, hiring pipelines, campaign reach to purchase.

Four qualitative stages for workshop enrolment, recruitment or sales.

Compare two cohorts through the same funnel stages: A/B test variants, this quarter against last, mobile against desktop visitors, two regions' hiring pipelines, two channels' sign-up journeys.

Three to five qualitative narrowing stages in buying, recruitment or investment screening.

Three to six narrowing stages such as acquisition, sales qualification, hiring, or filtering, with optional supplied count, percentage or amount labels in one consistent measure.

Suits processes where both drop-off and time matter: sales pipeline velocity, hiring pipelines, customer onboarding, support escalations, grant or approval processes.

For supplied daily activity over a compact actual date range: shipped orders, customer enquiries or campaign responses.

Suits retention and repeat behaviour of groups that started together: customers by signup month, employees by hiring class, buyers by first-order week, students by intake year, app users by install week.

Show how one measure varies across two lists, such as retention by signup week, activity by weekday and hour, or defects by team and month, with a number for each crossing.

Show pre-binned response times, ages, dimensions or prices with supplied counts in equal numeric intervals.

One center with three to eight parts that each tie directly to it, such as platform modules, strategy pillars, supporting teams, marketing channels, or product benefits.

For shared service offerings, campaign programs or community support.

For a core platform, team or offer and the four to eight parts that each depend on it directly, such as the services on a shared data platform, the departments around a customer team, the channels fed by one campaign, or the partners around a core product.

Successive enclosing contexts around one core, such as core, actual and augmented product benefits or named application layers.

One center and three to ten named ecosystem members, grouped into one or two supplied rings.

Two departments sharing a capability, partner ecosystems sharing a provider, or two regional networks sharing a facility.

One product, platform, team or idea and two to eight directly related capabilities, stakeholders or parts.

Customer or user journeys with stage-specific actions and observations, such as onboarding research or service design.

Appointment services, delivery experiences and student enrolment where each customer action has a supplied visible response and its corresponding hidden enabling activity.

A customer or user journey with three to six stages and stage-specific touchpoints, optionally with supplied feelings.

4–12 equal-weight points.

Named enclosing levels ordered from the core outward, with a description for each level.

Show 3–6 ordered layers of an iceberg: the first visible layer above a waterline and the remaining hidden layers below it.

Protection layers, a product core with its surrounding platform, or organizational spheres of involvement.

Cumulative support packages, learning stages or service coverage.

For a technology stack, an operating model from foundations to outcomes, or a layered security or service model, where each level supports the one above and owns a few named parts.

Country-level market amounts, recruitment figures or programme observations for the eight supported Central European countries.

Office support, regional coordination and service coverage between two to five catalogued cities in the fixed 40°E equatorial orthographic hemisphere.

A North American market-coverage overview for sales partnerships, recruiting coverage or distribution presence.

Sort named technologies, initiatives, product bets, regulations or market trends by an expected benefit level and the time horizon until it matters, as in an analyst priority matrix, an innovation radar summary, a product bet portfolio or a policy horizon scan.

For supplied qualitative choices of three or four options on exactly two opposed criteria: competing brands on personalisation and pace, vendors on cost model and support depth, product concepts on complexity and audience, or initiatives on effort and reach.

Service offers by delivery layer, brand pillars by evidence level, or skills by practice context.

Match audience to channel, urgency to contact method or customer type to service format.

Portfolio and prioritization views where position and size both matter: a growth-share product portfolio sized by revenue, projects by value and effort sized by budget, customer segments by frequency and spend sized by customer count, markets by attractiveness and strength sized by market size.

Show how one additive measure splits across two lists and which rows and columns carry the most, such as revenue by product line and region, support tickets by channel and weekday, headcount by department and office, or defects by component and release.

Three capability shifts, service priorities or portfolio moves on supplied zero-to-one-hundred scores.

Show where several capabilities, practices or controls stand on one ordered scale of three to five named levels, grouped into two to four domains, and how far each must climb to its target: a digital or data maturity assessment by domain, a security controls audit by control family, sales enablement skill levels by team, process or readiness reviews by function.

Entries sorted into four quadrants also carry one comparable amount: initiatives by impact and effort sized by cost, a product portfolio by growth and margin sized by revenue, accounts by fit and intent sized by ARR, markets by attractiveness and readiness sized by market size.

Entries are sorted by two categories, one of them a ring order from closest or core outward: an innovation ambition matrix (core, adjacent, transformational by business line), a technology radar by adoption ring and quadrant, stakeholders by proximity and group, partner ecosystem tiers by category, now, next and later by team.

Show where several capabilities, teams or practices stand on one ordered maturity scale and how far each must go: digital or data maturity, security posture, sales enablement, process or skills readiness.

Plans and observed shifts where entries move between positions: a portfolio repositioning plan by customer value and profitability, a capability shift by maturity and importance, accounts migrating by spend and engagement, markets moving by attractiveness and strength.

For customer needs and product features, event objectives and program choices, or workplace needs and site provisions.

Place named people, businesses, accounts, suppliers or products into the cell of two supplied three-level assessments: talent reviews (performance against potential), GE-McKinsey style portfolios (attractiveness against strength), account or supplier segmentation.

Supplied numeric axes, thresholds and quadrant meanings.

Tasks with supplied priority classifications under two binary criteria.

Four groups defined by two axes, such as a portfolio matrix, a skill/will grid, or a positioning map, where each quadrant needs a short explanation.

Capability readiness, venue assessment or curriculum evaluation using one supplied ordered scale.

Show where a set of risks, hazards or issues sits on a likelihood and impact scale and where treatment is expected to move them: programme and project risk registers, operational, security, compliance, supplier, health and safety or financial risk reviews.

Portfolio ownership; Channel planning; Service coverage.

Analyst-style evaluations where two scores on one scale decide standing: vendor or product evaluations (strategy against current offering), supplier and partner assessments, shortlisted solutions in a procurement review, agencies or candidates rated on two criteria.

For service queues, editorial work or project delivery.

Organize a launch plan, a learning curriculum or a venue programme into three peer branches with two ideas each.

Research planning, an operating-model outline or a learning curriculum.

One topic with 3–6 unordered branches and up to 3 subtopics each in a radial composition.

One topic broken into three to six themes with up to four short sub-items each, such as brainstorming a product launch, study notes on a subject, planning an event, or the areas of a strategy.

One topic broken into two to eight branches with up to five short sub-items each, such as a brainstorm, a study outline, a feature map, or the areas of a plan.

An ordered set of reasons, principles, tips or takeaways.

Choosing between approaches, tools, plans, or vendors with independent strengths and optional audience guidance.

A matrix product team, professional partnership or jointly managed project with supplied direct-report relationships to two leaders.

People grouped into two to five teams under one leader, with one to six members per team and up to twenty total.

A reporting hierarchy of three to twenty people over up to four levels, with at most six direct reports each, such as a company down to its team leads or a department down to individual contributors, with or without names.

A programme team, a workshop operation or a small venue with one lead, two managers and two reports per manager.

One leader over two to six teams with one to six people each and three to sixteen people in total, when the relative size of each team matters as much as who belongs to it: company departments under a CEO, hospital teams under a ward lead, club committees under a chair, project workstreams under a lead.

A service business with legal and finance advice, a school leadership team with specialist advisors, or a programme office with independent advisory roles.

A compact picture of three to twenty people over at most three levels, with up to six direct reports each, such as a small company's whole team, a department with its leads and members, or a committee, with or without names.

Three to fifteen people over up to three reporting levels, with two to five direct reports to the leader and up to five reports per manager.

Compare profiles across differently scaled or differently unit-bearing dimensions with explicit bounds.

Rank a supplied complete set of category counts and inspect their cumulative share.

A simple venue wayfinding infographic for an office visit, event venue or pop-up store.

Two to five plans, memberships, or packages with a price (or none), who each is for, and a few short key features, and optionally one recommended plan.

Compare three cumulative software plans, membership packages or support subscriptions.

Two to four plans or packages of one product with a price (or none), a few included features each, and optionally one recommended plan.

Negotiation exchanges, mentor and learner feedback, or client and agency creative review.

Preparation-to-launch activities, an onboarding sequence or a review process.

Show exactly three ordered conceptual stages: incoming work, the constraining stage, and outgoing work.

Recurring service review, replenishment operations and course improvement.

Idea refinement; Supplier screening; Campaign development.

For a compact three-phase business process such as a service launch, office move or campaign preparation.

For recruitment, editorial production or vendor onboarding.

Suits showing how inputs (raw materials, data, requests, ingredients, or factors) are transformed by a central process, engine, or system into outputs (products, insights, deliverables, or results).

For showing how much of a process's lead time is work and how much is waiting, in three to six ordered stages with a supplied work time per stage and a supplied wait between consecutive stages, all in one time unit: order fulfilment, hiring pipelines, loan or claim approval, feature delivery, support tickets, procurement.

Several paths share some steps and not others, and the reader needs to see where they meet and where each goes its own way: learning or career paths sharing core modules, onboarding tracks by role, product workstreams converging on shared milestones, customer journeys by segment sharing touchpoints.

For site selection, supplier screening, or program planning.

Event brief and acceptance, training needs and evaluation, or product requirements and verification.

Research and delivery work, exhibition content and operations, or learner practice and coaching.

For two ordered efforts that must both feed one shared milestone, review, decision or deliverable: product and marketing before a launch, research and engineering before a release, two teams before a merger or reorganisation, content and logistics before an event, legal and finance before a contract.

Decompose one supplied input into 2–5 distinct output perspectives through a triangular prism.

Four-stage onboarding, editorial production or product delivery.

Common content preparation into channels, data preparation into reports or shared induction into role-specific materials.

Editorial review, recruitment rework and proposal iteration.

For proposal development, onboarding plans or service assembly.

Campaign development; Service launch; Proposal preparation.

A campaign from research to release, a learning sequence from practice to application, or a service setup from discovery to delivery.

A learning progression, a product launch or a volunteer onboarding sequence.

Weigh one decision, product, approach, or choice by its advantages and drawbacks, with two to five of each and optionally a one-line verdict.

For any argument that connects one proposed claim to two or three supplied reasons and the specific support behind each: executive recommendations, offer pitches, research or policy summaries, hiring or investment cases, project proposals.

A capability pathway, a service hierarchy or levels of learning.

Broad-to-specific explanations, editorial hierarchies and narrowing priorities.

A supplied top-to-bottom hierarchy such as news-writing structure or broad-to-specific scope.

A familiar hierarchy with short tier-owned explanations: strategic direction to daily work, support escalation levels, or learning levels.

Three to six levels that build upward from a foundation, such as a hierarchy of needs, a maturity model, a data-to-wisdom pyramid, or a skills framework, when each level needs a short explanation.

A capability foundation, a service operating model or levels of a learning programme.

Strategy from purpose to daily action, learning from mastery to foundations, or ordered service tiers.

Strategy and delivery at each level, customer promise and operational evidence, or learning goals and practical activities.

Compare two supplied systems at the same ordered levels, such as two learning programs from foundations to advanced practice or two operating models from execution to strategy.

A supplied base-to-apex level hierarchy with a specific explanation for each level.

For strategy components, support models or learning pathways.

Supplied scores on comparable dimensions sharing zero and a common maximum.

3–10 supplied ranked entries, with ranks 1–999 preserved in order.

For effort or hours planned per period across overlapping work: a team's weekly person-days across a campaign launch, a crew's daily hours on a site fit-out, an agency's monthly billable days by client project, or support shift hours across a migration.

For a compact release plan, event preparation schedule or office move: two to five tasks across three to seven named periods.

Show how much work each period of a plan carries and which streams it comes from: a product roadmap by quarter and team, a Now / Next / Later plan by theme, a marketing calendar by half-year and channel or an operations plan by phase and site.

Three to fifteen pieces of work sorted by how soon they happen rather than by date, such as a product roadmap, a platform plan, or a team's priorities, with optional statuses and horizon notes.

For compact proposed plans across three named phases, such as an event, a product launch, a system migration, a hiring onboarding or a course redesign, with three to six work records and explicit adjacent-phase prerequisites.

Two to four teams, products or workstreams with two to sixteen scheduled initiatives across two to six supplied periods.

Three to seven milestones on the way to a goal, such as a product's path to launch, a growth plan, a learning path, or a customer's journey to adoption, with or without dates.

Two ordered sources allocating one common quantity to three ordered uses, with source one feeding use one or two and source two feeding use two or three.

Supplied flows of one common quantity from named sources to named destinations, such as traffic routing or expenditure allocation.

Two-variable observations, including signed, zero and coincident measurements.

Compare two or three options using supplied whole-number ratings from one to five across three to six criteria.

Two to eight options, vendors, candidates, or ideas rated on the same two to five criteria with whole-number scores out of three to five.

Show who talks to whom and in what order, such as an API call, a login or payment flow, or a handoff between teams, with up to fourteen messages between two to six participants.

Compare supplied observations for the same categories at two periods with a common unit.

Place items on an ordered scale between two poles, such as practices on a maturity scale, options from conservative to aggressive, or tasks from low to high effort.

The states a thing moves through and the events that move it, such as an order lifecycle, a ticket status, a subscription, or a device mode, including transitions back to an earlier state.

Supplied dashboard KPI sets such as revenue, active users, churn and latency.

Two to six separate supplied figures with labels and icons.

Individual supplied figures, preserving their currency, units, ranking and qualifiers exactly.

A supplied headline figure with supporting metrics.

Independent supplied completion, adoption, satisfaction or capacity percentages.

A compact dashboard of several metrics with a short shared history: monthly KPI reviews, product health or support operations metrics, regional or channel sales summaries, board pack scorecards.

A dashboard of several metrics that each have a short history over the same periods: monthly e-commerce or SaaS KPIs, weekly support or operations metrics, quarterly business reviews.

Two to eight items that each have the same few facts and, optionally, a status, such as projects with owners and due dates, services with uptime, or leads with priority.

Three to six stages that build on each other toward a goal, such as a maturity model, a career ladder, a growth plan, or levels of adoption.

Three to nine steps of one process that each need a few lines of explanation, such as a getting-started guide, a method, or a service delivery process.

An ordered process of two to six steps where two things happen at each step, such as what the customer does and what the team does.

Three to six sequential steps or phases that read left to right, such as a sales process, a delivery method, or an onboarding plan.

Three to five ordered process steps with hand-offs, such as approval, fulfillment, and request workflows.

Cumulative progressions where each level keeps what the previous ones established: maturity models, skill or career levels, service tiers, adoption stages.

Three to seven steps of one process read top to bottom, such as setup instructions, an onboarding checklist, or an incident procedure, where each step needs a sentence of detail.

Three to six steps of one process that read left to right, such as how a product works, a checkout flow, or a support procedure, where each step has its own icon.

Adoption maturity, professional progression or increasingly involved service levels.

Four to nine steps of one long process, such as a customer onboarding program, a product development lifecycle, or a hiring process, where a single row would be too wide.

A SWOT analysis of one company, product, team or plan when the internal/external split matters and a wide layout fits.

A compact SWOT for a programme, product launch or personal development.

Service positioning; Product launch assessment; Partnership planning.

A classic SWOT analysis of one company, product, team, or plan with two to six points per part.

A product launch, a community programme or personal development.

Connect supplied internal and external SWOT factors to proposed TOWS actions in their fixed intersections.

Plain tabular data of two to twelve rows and two to six columns, such as regional sales by quarter, a price list, specifications, or test results, with an optional supplied totals row.

Compare service packages by delivery mode, learning formats by provider group, or equipment variants by product family.

Show who does, owns, advises on and hears about each piece of work: product or campaign launches, process ownership, governance and approvals, onboarding plans, procurement or incident response.

Technical specifications, product data sheets, server configurations, vehicle attributes, device features, or model parameters for a single subject.

Supplied three-part percentages totaling 100, including pure components and coincident compositions.

A quick, punchy either-or between exactly two options, such as cats or dogs, tea or coffee, or two products, each summed up by a few one- or two-word tags.

A company story, a programme rollout or an exhibition schedule with three dated milestones.

For meeting agendas, event programs or training days with exact supplied local times.

Both when and how much matter: funding rounds over a company's history, product launches with first-year revenue, major contracts won, grants or donations received.

Events read best against the periods that frame them: a company history across leadership or strategy eras, product generations with their launches, policy or regulatory periods with key decisions, a career across roles.

For hiring windows, service availability or launch phases with supplied exact dates.

Three to eight dated moments in a history where the years matter most, such as a company's founding story, the history of a technology, a brand's heritage, or an organization's anniversaries.

Three to ten events in time order that each need only a few words, such as a release train, a trip itinerary, a customer's first week, an incident log, or a year of launches, with or without dates.

Three to eight milestones in time order that need a clean, typographic look, such as a product history, a launch plan, a release schedule, or key dates in a project, with or without dates.

A dated fortnight overview for campaign releases, training programmes or office moves.

A growth story told in consecutive multi-year phases where each phase has one supplied value of a shared measure, such as headcount or revenue by company era, users by product stage, population by city period or budget by programme phase, with a few dated milestones.

Product and company histories, two organizations around a partnership, or research and delivery histories with both independent and shared milestones.

Two to four parallel tracks (teams, products, or historical streams) across three to six shared periods with two to twelve total milestone events.

A product release calendar, a school programme or a hiring plan.

Two to eight scheduled phases across two to twelve supplied consecutive periods, such as a launch plan by month, a construction schedule by week, or a hiring plan by quarter.

Actual date-only milestones where horizontal distances should reflect elapsed days.

A product quarter, training term or community event season.

Conference tracks, parallel training workshops or a two-team rehearsal.

Three to eight milestones or phases in time order that read top to bottom, such as a project rollout, a product launch, a company history, or a migration plan, with or without dates.

Three to eight dated or undated events in time order that carry some text, such as a changelog, a company history, an incident log, a project schedule, or a career path.

Multi-year product milestones, annual programme cycles or recurring reviews.

Three to eight milestones or phases in time order, such as a project rollout, a product launch, a company history, an incident timeline, or a quarterly roadmap, with or without dates.

A many-to-one consolidation or replacement of three to eight current items into one to four successors, optionally retiring some: SaaS tool consolidation, vendor rationalization, squads regrouped into tribes, legacy systems decommissioned onto a platform, a product line simplified into fewer offers.

One observed or proposed change from one state to another, such as before and after, current and proposed, or old and new, with one to four independent points per side.

For compact two-level breakdowns of one subject: a goal into levers and actions, a product into capability areas and features, a program into workstreams and initiatives, or a topic into themes and examples.

Metrics that decompose into factors or parts: a profit tree (revenue minus costs), revenue as traffic times conversion times basket, unit economics, sales capacity as reps times quota times attainment, cost-to-serve breakdowns, or a productivity metric.

Suited for document outlines, folder structures, topic hierarchies, taxonomy trees, or feature breakdowns presented as a compact depth-first vertical list with structural guide lines.

A classification of four to thirty concepts under two to six root branches over up to four levels, such as a product catalog, content taxonomy or platform service catalog.