CIO Toolbox 2: Projects, Products, and Design Thinking Study Notes

Foundational Strategy and the Action Plan

In the context of the strategic process, the final output is an action plan designed to bridge the gap between current operations and strategic goals. This plan typically encompasses four primary elements: specific activities to modify or develop operations, the assignment of responsibility for these activities, an ordering or timeframe for execution known as a roadmap, and detailed estimates or budgets. In modern organizational discourse, there is significant debate regarding the appropriate level of detail for this planning. While some organizations advocate for precise, advance detailing and rigorous estimates, others prefer outlined activities that allow for emergent refinement. Regardless of the chosen detail level, the fundamental requirements for a functional working plan remain constant. Strategic change implementation can manifest through dedicated projects, organizational restructuring, or shifts in priority within day-to-day operations.

Different types of organizations share the same fundamental requirement to meet stakeholder expectations through administration and strategy. In private commercial organizations, stakeholders include owners and boards. Non-profits involve members and boards, while public organizations focus on citizens, politicians, and boards. For a Chief Information Officer (CIO), the ability to make informed choices is a critical capability. These choices range from high-level strategic decisions, such as determining whether to establish a new international office through hiring or acquisition, to tactical decisions like selecting a PC vendor.

The CIO Toolbox: Methods for Decision-Making and Development

The "CIO toolbox" is an informal and subjective set of methodologies used by CIOs to achieve organizational goals. It is emphasized that these tools are not ends in themselves but are only meaningful if they serve their specific purpose. Central tools in this collection include:

Business Case: Used for the prioritization of digital services and securing funding.
Alternative Analysis: A technique for vendor selection and product choice.
Design Thinking: Applied to prioritize services, funding, and selection processes.
IT Architecture: Used to analyze and structure the IT portfolio across systems and services.
Projects: Frameworks used to plan and organize development activities.
Product Teams and Agile Methods: Alternative frameworks to plan and organize development.
IT Governance: A system to distribute IT responsibilities among various organizational units.

Decision-making within this toolbox often relies on structured quantitative approaches. One popular method is the Business Case, which calculates the Net Present Value (NPV) of a given alternative. This calculation considers the annualized cash flow (expected income minus expected cost) and a risk premium representing the probability of variance in estimates. For example, considering a 5-year project:

$NPV_B = \sum_{i=1}^{5} \frac{200\,000}{1\text{.20}^i} - 350\,000 = 248\,122$

$NPV_A = \sum_{i=1}^{5} \frac{100\,000}{1\text{.12}^i} - 0 = 360\,478$

Another approach is the "plus/minus" method, an alternative analysis used for multi-criteria evaluation. For instance, in a data-sharing study, four options—K2 (Order in own house), K10 (Coordinated regional centers), K12 (Order in the educational sector), and K14 (The knowledge center)—were evaluated against investment costs (ranging from $50$ to $125$ ), financial costs ( $10$ to $30$ ), and benefits like reduced effort for consumers and data producers, and improved data protection. Each option was then ranked by cost, benefit, risk (Low to High), and real options (High to Low) to reach an overall evaluation score.

Project Management and the Case of Goodumbrellas Inc.

A project is defined as a temporary organization established to deliver one or more specified results or products within a specified period. The project approach allows for the easy involvement of multiple stakeholders in prioritization and the resolution of complex dependencies through careful planning. However, projects face significant challenges, particularly regarding the "triple constraint" of scope, cost, and time. Projects with fixed parameters in all three areas are especially vulnerable to disappointment. Funding is often granted based on assumptions of cost and benefits, and when risks materialize, it becomes difficult to differentiate between incompetent execution and unrealistic initial expectations.

Consider the hypothetical case of Goodumbrellas Inc., a company that produces umbrellas in Vietnam and sells through global retailers. Their new strategy is to establish a direct sales web channel (www.umbrella-heaven.com) with a goal that within $3$ years, at least $30\%$ of sales occur through this channel to increase profit retention. This strategic decision necessitates several activities: developing a web shop, establishing a warehouse for small on-demand orders, integrating with shipping providers for tracking, and creating online support and return capabilities. Implementing this through a project organization introduces challenges including legal issues, risk management, and coordination across production and sales divisions.

Complexity and the Cynefin Framework

To determine the right management approach, leaders can use the Cynefin framework (Snowden and Boone, 2007), which categorizes situations into four domains based on context:

Clear: Issues are well-known and solvable through agreed procedures or best practices.
Complicated: Cause-and-effect relationships are analyzable in advance; this is the "domain of experts" requiring analytical methods.
Complex: Important factors are unknown; experimentation and emergent practices are necessary to move toward a desired outcome.
Chaotic: Emergencies requiring immediate action to stabilize the state; results in novel practices.

Pinciroli (2024) elaborates that the selection of agile vs. traditional project management should be based on the number of fixed factors in the triple constraint and the presence of complexity factors. These factors include team skills (seniority, domain knowledge), project size and duration, requirement stability, client involvement, and the technology involved (known vs. unknown). The mapping for context selection is as follows:

Clear: $1$ to $2$ fixed triple constraint factors with $0$ added complexity factors.
Complicated: $1$ to $3$ fixed factors with $2$ complexity factors.
Complex: $1$ to $3+$ fixed factors with $2$ to $3$ complexity factors.
Chaotic: $1$ to $4+$ fixed factors with $2+$ complexity factors.

Design Thinking and Explorative Choice

Design Thinking (DT) is an explorative approach to innovation and problem-solving that connects creative design to traditional business thinking. It is not limited to the functionality of artifacts but applies to the form of businesses, services, and processes. A prominent model is the "Double Diamond," which consists of four phases:

Discover: Understanding the problem by spending time with people affected by it, rather than making assumptions.
Define: Reframing the challenge based on gathered insights. As noted by Wedell-Wedellsborg (2017), reframing is not about finding the "real" problem but finding a better one to solve, acknowledging that problems are often multicausal.
Develop: Co-designing and seeking inspiration to offer multiple answers to the defined problem.
Deliver: Testing solutions on a small scale, rejecting failures, and improving successful ones.

Product Teams and Agile development

Modern organizations, especially startups in Silicon Valley, are shifting from project-based work to autonomous product teams. Marty Cagan (author of Inspired, Empowered, and Transformed) highlights lessons for creating disruptive products, including storytelling to inspire passion through a product vision and ensuring continuity by creating lasting teams instead of temporary projects. These teams focus on outcomes (the results achieved) rather than outputs (the amount of work done).

Key takeaways for product environments include:

Applying Design Thinking early and often.
Expecting and being prepared for pivotal change.
Granting teams autonomy to innovate.

However, autonomous teams face challenges in multiteam environments, such as balancing alignment with autonomy, measuring the right degree of autonomy for different contexts, and adjusting agile practices for cross-functional effectiveness. Examples of this in practice include the "Autosys" modernization project, which combined a traditional business case with autonomous product teams for self-service functions, and Spacemaker (Autodesk), which chose "a little chaos over control and big platform architectures" to prioritize "time to value."

There is no evidence that one approach—projects or product teams—is universally superior. The choice depends heavily on the context: improving an operational backbone may require different tools than developing a new digital offering. Ultimately, any approach benefits from passion and effective storytelling to align and inspire the organization.