Pardon our construction as we are upgrading the site to bring you more of the type of information you are searching.  Please try back later. 

Select the search type
  • Site
  • Web

Wardley (Value Chain) Mapping

Anticipating the Future - A Map to Navigate From, and Drive a Better Customer Experience

  • 2 February 2015
  • Author: Simon_Wardley
  • Number of views: 0
Wardley (Value Chain) Mapping
Wardley Mapping (called also Value Chain Mapping) is a technique of environment visualization that lets you to replace copying competition and gut feeling with a conscious strategy covering even things you do not know and enable you to do do things like:

  • reduce the cost of a single project up to 30%
  • find and identify new business opportunities
  • capture market share with minimal investment
  • identify and remove risks

Reference:   http://www.wardleymaps.com/    

Tool:  https://github.com/cdaniel/wardleymapstool    

Video: https://www.youtube.com/watch?v=NnFeIt-uaEc 

Step 1. Needs!
Step 2. Value Chain!
Step 3. Map!
The first part of mapping is to improve situational awareness i.e. it's useful to have some in the first place. When you've written a map that's not the end because maps are dynamic and will change over time.

Step 4. Challenge!
Step 5. Adjust!
The second part of mapping is to challenge what we think the situation is, remove duplication and bias. This involves sharing maps with others, refinement (including metrics where needed) and adding in aggregate perspectives (our own historical repository of how we treat things).

Step 6. Think!
Step 7. Methods!
Step 8. Simple!
Step 9. Evaluate!
The third part of mapping is to decide to do something, the strategic play, how we're going to do it, how we're going to organise it. The last bit - evaluate - is usually to create those evaluation artefacts (SWOTs, BMC) that others seem to sometimes require in order to bring them along. It can be useful but often I find that last step unnecessary, time consuming and often omit it.

Step 10. Act
The last bit of mapping is to get on with it, get started. This is not the end of the story though, you have to continuously iterate all the above.

Read more


Handling Complexities with the Simplest Solution of Checklists

Agile Checklist:  "Checklists reduce my flexibility, creativity, spontaneity; or they are too bureaucratic."  The argument can be refuted by recognizing that any tool can be misused.  Rigidly enforced, top-down, heavy-handed, compliance-oriented, slavishly-followed checklists will indeed create problems; but highly customizable checklists developed by professionals and teams of professionals doing the work, supported by appropriate tool, and used by those empowered professionals can be very helpful.  These kinds of smart checklists will take the drudgery and errors out of complex work, and thus, freeing up time for creative work.     Wikipedia: "A checklist is a type of informational job aid used to reduce failure by compensating for potential limits of human memory and attention. It helps to ensure consistency and completeness in carrying out a task. A basic example is the "to do list." Examples of more advanced checklists would be a schedule or KanBan which lays out tasks to be done according to time of day or other factors." Examples: Dr. Atul Gawande's TED Talk; How do we heal medicine?  and How the Pilot's Checklist Came About


Web Sequence Diagrams


Web Sequence Diagrams
Create sequence diagrams faster than on a whiteboard, by writing them in your Docs. Sequence Diagrams let you describe how different parts your system communicate with each other. But drawing sequence diagrams can take hours with traditional tools. Your clients and colleagues will be impressed if you can make large-scale changes as easily as copying and pasting text, instead of spending your time moving lines around with a mouse. With this add-on, you write your sequence interactions directly into your documentation. With a click of the button, they are converted into professionally formatted UML sequence diagrams in a variety of styles.

Solution Envisioning

A business-value focused, scenario-driven approach using analogies and examples using Capability Cases

Solution Envisioning
Solution Envisioning is a problem discovery, situation assessment and solution planning process that uses Capability Cases to achieve connections between Business and IT stakeholders.  It was designed to improve chances of solution success by addressing the risks and challenges present in the early stage of the solution lifecycle. Solution Envisioning embraces a business-centric approach to designing and realizing technology enabled business capabilities.   It truly ‘bridges the gap’ between business and IT by integrating and marrying concepts and techniques from both best of breed business strategy methods and software development methods. By identifying patterns through quantitative classification in  "design by example" workshops where analogies and brainstorming make for the best possible solution.  The patterns allow for workshop members to say, “What we want is something like this"

Laws, Regulations, Policies (LRP) Library

Leveraging LRPs in Requirements, Operations, and Risk Management

Laws, Regulations, Policies (LRP) Library
A LRP repository capability is the quasi-authoritative source to ensure personnel are aware their activities and of the applicable laws, regulations, and policies (procedures, instructions, directives, orders, circulars, memorandums, etc.) in developing requirements baselines, operational guidance, and risk management criteria. LRP requirements are the minimum set of prerequisites for the baseline, in essence LRP are approved implementation constraints. LRP Library becomes one foundational aspect of the requirements management process. To aid operations, some organizations have aligned the LRP content to the business architectures to allow for easier linking policy to operations. The LRP Library supports the processes and rules to adopt, implement, and monitor an integrated business environment. Applied to risk management organizations have a better understanding on potential risks and allows for the prioritization and mitigation strategies based on the organization's business objectives and needs.