project-half-double

Project Half Double In A Nutshell

Project Half Double is a contemporary management methodology with a focus on value creation. Project Half Double is a methodology created by the Half Double Institute, a Danish non-profit foundation with the goal of increasing the success rate of projects all over the world.

AspectExplanation
DefinitionProject Half Double is a project management approach and methodology that aims to significantly improve the performance and impact of projects. Developed in Denmark, it focuses on simplifying project management practices to achieve better results with less effort. The “Half Double” name reflects the aspiration to cut project duration in half while doubling the impact, value, and joy of project work. This approach combines principles from Lean and Agile methodologies with a focus on leadership, impact, and flow. Project Half Double emphasizes the importance of project purpose, flow efficiency, and leadership engagement. It is designed to make projects more adaptable, responsive, and effective, ultimately delivering better outcomes.
Key ConceptsImpact: Project Half Double prioritizes the achievement of meaningful impact and value as the primary project goal. – Flow Efficiency: It emphasizes streamlining project processes to improve flow and reduce waste. – Leadership Engagement: Engaged leadership is seen as essential for project success. – Pulse: Projects are managed in pulses or cycles, allowing for adaptation and continuous improvement. – Empirical Mindset: It encourages a mindset of experimentation and learning from project experiences.
CharacteristicsImpact-Driven: The approach places a strong emphasis on defining and measuring the impact of a project. – Lean Principles: Project Half Double incorporates Lean principles to eliminate waste and enhance efficiency. – Leadership Involvement: Engaged leadership is crucial for creating a conducive project environment. – Pulse-Based: Projects are managed in iterative pulses, allowing for frequent assessment and adaptation. – Learning Culture: It promotes a culture of continuous learning and improvement within project teams.
ImplicationsIncreased Impact: Project Half Double aims to deliver projects with significantly greater impact. – Efficiency Gains: Lean principles result in improved process efficiency and reduced waste. – Engaged Leadership: Leadership involvement contributes to a more supportive and adaptive project environment. – Adaptability: Pulse-based project management enhances adaptability to changing circumstances. – Learning Culture: Encouraging a learning culture leads to ongoing improvements in project practices.
AdvantagesHigher Impact: Projects are designed and executed with a focus on achieving more significant impact and value. – Efficiency: Lean principles lead to increased efficiency and reduced resource waste. – Leadership Support: Engaged leadership fosters a supportive and adaptive project environment. – Adaptability: Pulse-based project management allows for quicker adaptation to changes. – Continuous Improvement: A learning culture results in ongoing enhancements to project management practices.
DrawbacksCultural Resistance: Implementing Project Half Double may face resistance in organizations accustomed to traditional project management. – Complexity: It can be challenging to fully integrate Lean and Agile principles into existing project management practices. – Resource Requirements: Transitioning to this approach may require additional resources for training and cultural change efforts. – Limited Applicability: Not all projects may benefit equally from the approach, and adaptation is necessary. – Change Management: Cultural and process changes require effective change management strategies.
ApplicationsComplex Projects: Project Half Double is suitable for complex projects that require adaptability and focus on impact. – Innovative Initiatives: It can be applied to innovative projects aiming for significant market impact. – Process Improvement: Organizations use it to improve project management processes and efficiency. – Change Projects: Projects involving significant organizational change can benefit from the adaptability of this approach. – Social Projects: Project Half Double is also used in social projects with a strong focus on societal impact.
Use CasesProduct Development: A technology company adopts Project Half Double for a critical product development project. The project team focuses on achieving a higher market impact while streamlining their processes to eliminate waste. – Market Entry Strategy: A multinational corporation uses this approach to plan and execute an innovative market entry strategy. The pulse-based management allows for quick adjustments to the ever-changing market conditions. – Process Improvement: An organization applies Project Half Double to its project management processes, reducing inefficiencies and enhancing overall project outcomes. – Organizational Change: During a major organizational restructuring, a company employs this approach to manage the change projects effectively, adapting to evolving circumstances. – Social Impact Initiative: A nonprofit organization utilizes Project Half Double for a social impact initiative, concentrating on maximizing the societal benefits of the project and continuously learning and adapting based on the project’s outcomes.

Understanding Project Half Double

The methodology – which has been validated across various industries and projects – is partly based on the unpredictable and complex nature of human behavior. In other words, Project Half Double does not assume that the behavior of team members, stakeholders, clients, and customers are predictable or indeed rational. Managing human behavior is seen as vital in making maximum impact and ensuring that projects flow as smoothly as possible.

It’s important to note that Project Half Double is not a blanket approach, even though human behavior is consistent across organizations. Half Double elements can be adapted to suit the systems or desired culture of any organization.

The three core elements of Project Half Double

Project Half Double is based on three core elements:

Impact

The Project Half Double philosophy stresses that project deliverables are not the end goal and that projects do not exist for their own sake. Instead, teams should focus on the impact (effect) that these deliverables make on the world. 

Here, businesses should measure their success based on stakeholder satisfaction. They should be less concerned with how quickly or cost-effectively they can deliver the final product.

To maintain a focus on value, teams can utilize tools specific to Project Half Double including KPI tracking, consistent stakeholder contact (“pulse checks”), and impact solution design templates.

Flow

Half Double acknowledges that projects are invariably demanding on team members. It seeks to ease this burden by selecting suitably skilled staff and ensuring that each project is well funded and resourced. 

Ultimately, the focus of the flow element is on making progress through creativity, collaboration, and rapid feedback loops. Saving money is acknowledged as less of a concern if there is a focus on frequent interaction within the team.

Tools that support flow include the visual planning of project vitals and the creation of project rhythm through the progression of regular project sprints.

Leadership

Project Half Double understands that individual team members are complex. They have shifting agendas and are driven by unique and sometimes irrational motivations. The world in which project teams operate is similarly chaotic, irrational, or unpredictable.

As a result, leadership must embrace the uncertainty of human behavior while ensuring that progress is made in alignment with goals and objectives. Leaders should embrace change and uncertainty as an avenue for growth and not fight against it. This means less of a focus on bureaucracy, formal meetings, and contractual obligations.

Tools to enhance leadership revolve around creating a reflective and adaptive mindset that favors problem ownership and collaborative management.

Project Half Double case studies

Although a relative newcomer to the suite of agile-inspired frameworks, the Half-Double approach has been successfully implemented in several pilot projects:

  1. Manufacturing company LINAK. Here, Project Half Double was used to improve project execution time from 60 to 39 weeks. This was achieved through greater collaboration with suppliers, who delayed project delivery because of the time and cost associated with traveling to LINAK for factory acceptance tests. LINAK leadership teams agreed to share the cost and for traveling and accommodation with supplier staff, ultimately improving relationships and productivity.
  2. LEGO group. Danish toy manufacturer LEGO also used Half Double principles to increase stakeholder engagement through the hosting of solution hypothesis workshops. Furthermore, the company incorporated pulse checks to give team members more opportunities to address project challenges. To increase impact, teams of five people now spend 40% of their work time housed in specially designed rooms to facilitate high-intensity work on a single project.

Key takeaways

  • Project Half Double is a contemporary project management methodology that favors value creation over project deliverables.
  • Project Half Double comprises three core elements: impact, flow, and leadership. Core elements work together to facilitate sometimes unpredictable agile projects that are adequately funded with suitably skilled team members.
  • Elements of Project Half Double have been used by toy manufacturer LEGO to increase stakeholder engagement and give team members more opportunity to raise project concerns and challenges. 

Key Highlights

  • Introduction to Project Half Double:
    • Project Half Double is a modern project management methodology developed by the Half Double Institute, a Danish non-profit foundation.
    • It focuses on enhancing project success rates by emphasizing value creation and addressing the complex and unpredictable nature of human behavior.
  • Foundation and Validation:
    • The methodology has been validated across diverse industries and project types, recognizing that human behavior, including that of team members, stakeholders, clients, and customers, is not always predictable or rational.
    • Project Half Double aims to maximize impact by effectively managing human behavior within projects and ensuring smoother project execution.
  • Adaptability and Customization:
    • While Project Half Double acknowledges the consistent nature of human behavior across organizations, it allows for customization to fit the specific systems and desired culture of each organization.
    • Organizations can adapt Half Double elements to suit their unique context while maintaining the core principles.
  • Three Core Elements:
    • Impact: This element shifts the focus from project deliverables to the impact these deliverables have on stakeholders and the world. Success is measured by stakeholder satisfaction rather than just delivery speed or cost-effectiveness.
    • Flow: Recognizing the demands on project team members, Flow ensures proper resourcing, skill alignment, and funding. It emphasizes progress through collaboration, creativity, and iterative feedback loops.
    • Leadership: Acknowledging the complexity of individual motivations and the unpredictable nature of the project environment, Leadership embraces uncertainty and change. It promotes an adaptive mindset, problem ownership, and collaborative management.
  • Tools for Each Core Element:
    • Impact: Tools include KPI tracking, consistent stakeholder engagement (“pulse checks”), and impact solution design templates to ensure projects align with stakeholder needs.
    • Flow: Visual planning of project elements and regular project sprints create a project rhythm that fosters collaboration and maintains momentum.
    • Leadership: Tools focus on developing a reflective and adaptive leadership style that supports problem-solving and embraces uncertainty as a growth opportunity.
  • Project Half Double Case Studies:
    • LINAK: A manufacturing company that improved project execution time by collaborating more closely with suppliers, sharing travel costs, and enhancing relationships. This reduced project time from 60 to 39 weeks.
    • LEGO Group: The Danish toy manufacturer used Half Double principles to increase stakeholder engagement through solution hypothesis workshops. Pulse checks enabled better addressing of project challenges, and dedicated project workspaces promoted focused teamwork.
  • Key Advantages:
    • Value-Centric Approach: Project Half Double prioritizes creating value over simply delivering projects.
    • Holistic Management: The three core elements work synergistically to create a holistic management approach that accommodates human behavior and project complexities.
    • Adaptive Leadership: Leadership within Project Half Double embraces uncertainty and change, promoting collaborative problem-solving and growth.
  • Applicability and Future Outlook:
    • The methodology’s principles align with contemporary leadership and agile practices, making it adaptable and relevant in today’s dynamic business environment.
    • Project Half Double can be applied not only to traditional in-person settings but also in remote work contexts through digital tools and virtual engagement.

Connected Agile Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

AgileSHIFT

AgileSHIFT
AgileSHIFT is a framework that prepares individuals for transformational change by creating a culture of agility.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Program Management

agile-program-management
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Bimodal Portfolio Management

bimodal-portfolio-management
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.

Business Innovation Matrix

business-innovation
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Constructive Disruption

constructive-disruption
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

ICE Scoring

ice-scoring-model
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.

Innovation Funnel

innovation-funnel
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.

Innovation Matrix

types-of-innovation
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).

Innovation Theory

innovation-theory
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrumban

scrumban
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Stretch Objectives

stretch-objectives
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.

Waterfall

waterfall-model
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework. 

Read Also: Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: Agile Methodology, Lean Methodology, Agile Project Management, Scrum, Kanban, Six Sigma.

Main Guides:

Main Case Studies:

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

Scroll to Top
FourWeekMBA