The Customer Card

It’s never been as important to reach outside of the business as it is in the digital world of today. From an architects perspective it is vital to be able to connect the dots between what is servicing and who is being served. This little card is designed to help you go fast by staying small and keeping it nimble. The design of the card does some heavy lifting by tying the outside to the inside through services and value requirements.

The_Customer_Card

This Customer Card contains an example to make it easier for others to use the template card.

When you should use this

  • Whenever you need to understand the service and how you are servicing the customer
  • When you need to keep a trail from customer to service and deeper into the architecture

What you should consider when you use this

  • Use this is a guide, change it to fit your needs
  • Print many small copies and put in the hand of those who knows the customer
  • Print many large copies and put them on walls
  • This card is best used as a communication tool in collaboration between teams

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Download
You can download the presentation here

Related

Post change log
2015-11-03: Published initial post

Advertisements

The Idea Card

Whatever business you are in innovation is the name of the game. Today it’s even more important than ever that you innovate fast and somewhat accurate. This little card is designed to help you go fast by staying small and keeping it nimble.

The_Idea_Card

When you should use this

  • Whenever you need to innovate
  • When you need to keep a trail of successful and failed ideas

What you should consider when you use this

  • Use this is a guide, change it to fit your needs
  • Print many large copies and put the on walls
  • This card is best used as a communication tool in collaboration between teams

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Download
You can download the presentation here

Post change log
2015-10-29: Published initial post

The Entity Card

Whatever business you are in, information is the most important raw material there is and it should be understood by many. Using tools like the entity card is one way of communicating on relatively stable information structures, there are other ways. People may say this is hard and takes a lot of time todo. To them I would recommend that they think about the basic information used in the business and evaluate for how long the average entity has been around. My experience is that most entities within a business domain has been around at least +80% of the lifetime of that domain. Changes to the entity is almost always on business rule or attribute details.

The Entity Card

When you should use this

  • Whenever you set about designing an entity you can use these questions to understand the shape and use of the entity in scope
  • When you need to document in some detail a key entity

What you should consider when you use this

  • Use this is a guide, change it to fit your needs
  • An entity in the overall information architecture is just one piece of the puzzle
  • This card is best used as a communication tool in collaboration between agile teams and architects

 

License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Related

Post change log

2015-10-15: Published initial post

Using the Capability Inventory for municipalities

Using the Capability Inventory for municipalities

I was talking to Marino the other day and he told me he would like a special capability inventory for a municipality. I said that there is no need to have a special capability inventory, the basic pattern exposed in the original capability inventory should cover any organization. In fact he should just use the original one and perhaps add the elements that are missing. The basic pattern behind the capability inventory is to view every organizations output as delivering services. This view enables us to use the same basic elements across all organizations. I can relate to the fact that the pattern and elements looks unfamiliar because it does not follow the way one is used to visualize a municipality. To remedy any confusions I´ve designed a naïve example below.

Elaborating on the capability inventory for municipalities
Elaborating on the capability inventory for municipalities

In the example I´ve removed the elements in the envision and enable rows and focused on the engage row. The text in the capability elements are not capabilities rather they describe the activities one would perform using the capability to reach the business goals.

When you should use this

  • Whenever you set about using a capability model of your enterprise
  • Whenever you have a new business problem to consider

What you should consider when you use this

  • Using the capability inventory and mapping out the basic activities will give you a good hunch but it is not the complete constructs needed to design the business.
  • It took me about 15 minutes to whip up the example

Download note

I’m currently in a process of changing my presentation design (the images shows what the new design looks like) for all my work. When I’ve stabilized the design and applied it across all canvases and related material I’ll link up the powerpoint to Slideshare.

License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Related

Post change log

2015-07-02: Published initial post

The Capability Inventory

This model is part of my toolbox for working with capability architectures.

The Capability Inventory

I know that there is certain ways of naming a capability and also that there are other principles that people and I promote that you should adhere to when designing your capability map. Here I’ve taken some liberties in regards to those principles to make it easier to relate to the possible content in the boxes. This inventory is basically what I refer to as “functions as capabilities“, now there is certainly a way of mapping proper capabilities into this inventory.

The Capability Inventory Details 

Detailing production
Details of production capability

Philip asked about the production capabilities so I’ve detailed some parts of production (above) to show where they could be situated. The detailed inventory map also shows how one can reuse the original layout to keep things in view.

Details of the sales capability
Details of the sales capability

 

Details of the marketing capability
Details of the marketing capability

 

I have some more of these laying around in different formats and states of publicity. When I find the time I’ll update this post with more of these.

Download note: I’m currently in a process of changing my presentation design (the images shows what the new design looks like) for all my work. When I’ve stabilized the design and applied it across all canvases and related material I’ll link up the powerpoint to Slideshare.

When you should use this

  • Whenever you set about designing a capability model of your enterprise
  • When you need to understand what types of capabilities an enterprise can have
  • When you are set to create a target context map for microservice architectures

What you should consider when you use this

  • This is not “the complete, nor the correct” inventory of capabilities
  • There is no known right way of designing or describing a capability of an enterprise
  • There is techniques like reversing the names of processes and then consolidating them that could give you a fair hint of what capabilities you have in your enterprise
  • Look at other peoples capability inventories and take inspiration from those
  • The “best” capability inventory is the one you get enough people to use in their work
  • Develop the capabilities and the capability inventory in as wide spread community as possible
  • Continuously refine your capability inventory as you go
  • When naming capabilities think of each capability as part of a namespace
  • In the end it’s all about just doing it

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Related

Post change log
2015-06-15: Published initial post
2015-06-20: Added the detailing view of production
2015-06-22: Added the detailing view of sales
2015-06-23: Added the detailing view of human management
2015-06-23: Updated the basic inventory of capabilities to reflect the sales capabilities directly
2015-06-24: Added the detailing view of marketing

The Inventory Model

This model is part of my toolbox for working with business architectures.

The Inventory Model

THE ENTERPRISE INVENTORY

 

The important thing to remember is to be agile minded in use of tools like this. So, when I say extendable I mean that this is definitely not all things that could or should be in the inventory. Reconfigure it in the X, Y or Z axis as you see fit for purpose and make sure to deliver something of value.

Note: I’m currently in a process of changing my presentation design (the image shows what the new design looks like) for all my work. When I’ve stabilized the design and applied it across all canvases and related material I’ll link up the powerpoint to Slideshare.

When you should use this

  • Whenever you set about depicting the greater enterprise

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Post change log
2015-05-19: Published initial post

The Strategy Model

This model is part of my toolbox for working with strategic architectures.

The Strategy Model

The Strategy Model

 

Note: I’m currently in a process of changing my presentation design (the image shows what the new design looks like) for all my work. When I’ve stabilized the design and applied it across all canvases and related material I’ll link up the powerpoint to Slideshare.

When you should use this

  • Whenever you set about understanding the greater enterprise

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Post change log
2015-05-12: Published initial post

The Scenario Canvas

This little canvas is part of my toolbox for detailing and documenting scenarios.

The Scenario Canvas

The Scenario Canvas

 

Note: I’m currently in a process of changing my presentation design (the image shows what the new design looks like) for all my work. When I’ve stabilized the design and applied it across all canvases and related material I’ll link up the powerpoint to Slideshare.

When you should use this

  • When designing target architectures I tend to use scenarios in conjunction with capabilities to help navigate the uncertainties of the future. (How this is done will be covered in a later post)
  • In the HBR article Living in the futures, Angela Wilkinson and Roger Kupers highlight how Shell has used scenarios.
  • In the McKinsey article The use and abuse of scenarios, Charles Roxburgh highlights some great insights into when and how to work with scenarios.
  • In the Forbes article Scenario planning and strategic forecasting, Jan Ogilwy presents a way of doing scenarios and also an interesting graph on what tools people use to peak into the future.

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Post change log
2015-04-26: Published initial post

The Capability Canvas

Designing businesses is not a trivial activity. Having a simple structure that one can use to design and / or understand a capability makes designing business architecture so much easier.

The Capability Canvas

The Capability Canvas 2015-02. Click image to view powerpoint presentation on Slideshare
The Capability Canvas 2015-02. Click image to view powerpoint presentation on Slideshare

When you should use this

License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Change log
2015-02

I’ve cleaned up the descriptions of the elements to make it easier to work with.

  • PROCESS – Renamed “using” to “associated with ”.
  • SERVICE – Renamed “enabled” to “associated with ”.
  • INFORMATION – Renamed “produced, consumed and manipulated by” to “associated with ”.
  • TECHNOLOGY – Renamed “supporting” to “associated with ”
  • ORGANISATION – Changed spelling to US format.
  • VALUE – Renamed “attributed to” to “associated with ”
  • INVESTMENT – Renamed “we have done, do or plan to do on” to “associated with ”