Business Solution Canvas

From BTMap
Revision as of 14:43, 1 February 2022 by AndreasLeue (talk | contribs) (→‎Positionierung)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search



The Business Solution Canvas ( is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License. To view a copy of this license, visit or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. It is inspired by the Business Model Canvas (, which is available under the same license. The Business Solution Canvas was created by Andreas Leue (


What is a Solution?


  • A process: it solves a repeated set of tasks systematically
  • A service: it solves on-demand a specified task
  • A software installation: it solves a complex business function
  • A software product: it solves a certain kind of common business function


Sue did it. She's tired, but she did it. 18 hard month, full of work, day and night, talking, endless talking; sketching on flipcharts, discussions, spotting for teammates and opportunities all around the clock. Now the paperwork is done, the sparkling wine drunken and many hands have been shaken: Sue's new business is rolling.

Sue's experienced, the hands-on type. She's not so much in finance and policy, so she paired with Ken. Ken quit his all-to-boring job for what he calls his first true adventure in live. He's sitting all day in front of Excel and his phone now, while Sue's running around getting man and machine do something useful.

Still there's this tiny little Post-It lurking on the wall in the "Key Activities" part of her Canvas. It's looking at her. Staring. It says "Platform Development".

Not that this platform is something particularly special. It's just a damn, custom web service. That has to be an easy job. Her first encounter with sales people from Money Pile IT was somewhat disappointing. They somehow mistook her with someone else - it has to be the only valid explanation for their offer.

The two handsome guys from Die In Slices at first sounded promising, at least they seemed to be interested in what's going on here - yet they wouldn't let her fix a single fact.

(to be continued...)


  • Wem soll die BSC nutzen?
    • Fachanwendern
    • IT
    • Leuten an der Schnittstelle
  • Was soll die BSC nutzen?
    • eine Brücke bauen zwischen stark-strukturierten IT-Modellen und nahezu unstrukturierten Stories
    • ein einheitliches, extrem einfaches Mittel bereitstellen, um gesamtheitlich auf Lösungen zu schauen
    • gesamtheitlich heißt: Ziele, Stakeholder, Prozesse, Vorgehensweisen, Daten, Zeitrahmen, Lokation, Risiken/(Chancen), Kosten


  • einen Einzelprozeß im Unternehmen skizzieren (Lean Activity/Process)
  • Anforderungen an eine Software-Lösung festhalten (Lean Pflichtenheft)
  • Anforderungen aus BMC, CJC usw. lean-anschlußfähig ausspezifizieren (Lean EAM)


  • Welche Felder soll die BSC enthalten?
  • Wie sollen die Felder angeordnet werden?
  • Welche Form soll sie haben? (rund, eckig...)
  • Welches Layout? (angelehnt an BMC? oder eher SDT/CJC? ganz anders?)
  • Sollen "typisierte" Post-Its verwendet werden?
    • farbig? Icons? verpflichtend? nur in unseren Beispielen?
  • Welche Informationen sollen als Feld eincodiert werden?
    • Alternative: getagged mit PostIts?
    • z.B. Schedule: eigenes Feld, oder auf PostIts an die Elemente gehängt?

Graphic Design

  • BMC like (see below)
  • CJC like (see below)
  • different?


  • Verhältnis zu Agile/Lean
  • Verhältnis zu User Stories/Epics
  • Verhältnis zu Story Board
  • Verhältnis zu Customer Journey Canvas
  • Verhätlnis zu SDT (Service Design Thinking)
    • SDT/CJC: fokussiert auf Kundenproblem-Lösungseigenschaften-Match
    • BSC fokussiert auf Umsetzung, Machbarkeit, sprich Anforderungs-Lösungs-Match
  • Verhältnis zu BA
    • BSC ist: Agile Analysis
  • Verhältnis zu EAM
    • BSC ist: Lean Architecture
  • Verhältnis zu BPMN
  • Verhältnis zu UML
  • Verhältnis zu UBPML
  • Verhältnis zu MDT

business solution canvas positioning.svg


Recommended background reading:


Related Agile/Lean stuff