Background

How to determine objectives for capability development: 3 easy steps

How to determine objectives for capability development: 3 easy steps

An organization deploys capabilities to execute its activities. Some of these capabilities are critical to survive and thrive. You can determine objectives in three easy steps to steer the development of critical capabilities in your organization.

How to determine objectives for capability development.

Steps to determine objectives

Advantage

Define which advantage the capability will bring to your organization.

Direction

Define a course of action for developing the capability in your organization.

Priority

Define the importance and urgency of developing the capability.

Advantage

To identify the advantage that a capability brings to your organization, you can perform a VRIO analysis. This allows you to find out four relevant properties. These properties are:

Valuable

Able to exploit opportunities and defend against threats.

Rare

Scarce and difficult to acquire.

Inimitable

Hard to copy or substitute.

Organized

Set up to capitalize on resources.

Direction

Determine a course of action for developing a certain capability as follows:

Produce

If it is valuable but not present in your organization.

Specialize

If it is valuable and present but not rare in the market.

Integrate

If it is valuable, present, and rare but imitable for competitors.

Multiply

If it is valuable, present, rare, and inimitable but vulnerable in your organization.

Maintain

If it is valuable, present, rare, inimitable, and organized.

Stop

If it is present but no longer valuable to your organization.

Priority

There are several ways to prioritize. There is no best way, as it all depends on the context. When pursuing an Agile way of working, determine a priority for developing a certain capability as follows:

Now

To be developed first.

Next

To be developed next.

Later

To be developed later.

Posted by Pieter van Langen in Background
7 sorts of knowledge that determine the power of design

7 sorts of knowledge that determine the power of design

Designers continually develop knowledge with customers, commissioners, users, fellow designers, partners, and other stakeholders. They acquire, create, and share knowledge of different sorts. This post explains which sorts of knowledge a team needs to accomplish design work.

Sorts of knowledge.

Sorts of knowledge

A team’s organization rests on the following sorts of knowledge and their inter­relation­ships.

  • Strategy: the plan to accomplish design goals.
  • Structure: the way of organizing design work.
  • Systems: processes and procedures of design.
  • Style: the way designing is approached.
  • Specialisms: fields of specialization of designers.
  • Skills: talents and abilities of designers.
  • Shared values: accepted values, norms, and standards for designing.

7 sorts of knowledge that determine the power of design 1

These seven sorts almost entirely correspond with the seven internal factors in the McKinsey 7S Model. Other points of departure are conceivable, but the McKinsey 7S Model applies well in practice. Furthermore, many managers know this model. For a brief introduction to this model, see, for instance, Strategic Management Insight or Investopedia.

In practice, the two sorts Systems and Style can be hard or unnecessary to distinguish. For instance, a design team may define style as the processes and procedures the team members are used to follow. In such cases, you may conveniently combine the two sorts into one sort, System.

Framework for design knowledge

The seven sorts of knowledge and their interrelationships form a framework that can be used to:

  • Analyze a design activity.
  • Grow knowledge that is of interest to design work.
  • Make design knowledge part of a team’s DNA.
Posted by Pieter van Langen in Background