GIST Planning And Why It Matters In Business

GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.

Understanding GIST Planning

As a product manager, Gilad understood that there can sometimes be a mismatch between product planning and reality. While product roadmaps such as Gantt charts help to some extent, these approaches are vulnerable to change initiated by top-down management. Indeed, the net result of these directives is often the replanning or cancellation of certain projects.

The four blocks of GIST Planning

GIST is built on an acronym consisting of four blocks. Each block has a corresponding planning horizon and frequency of change.

Collectively, project teams must understand that the four blocks encompass a core planning methodology that must be followed in its entirety.

Let’s now take a look at each of the four blocks in more detail:

  1. Goals. Where does the company want to be, and when? How will the company know when it has got there? Goals should ultimately coincide with the reasons for a company undertaking a particular project.
  2. Ideas. In GIST Planning, ideas are hypothetical ways to achieve goals. Product managers must create a dedicated idea collection system in the form of an “idea bank”. Here, brainstormed ideas are stored and then prioritized using the ICE Scoring Model or other prioritization frameworks.
  3. Step-projects. Many teams make the costly mistake of picking a promising idea and immediately executing on it. Without proper due diligence, the team ends up investing heavily in an idea that was never worth the investment. To reduce risk, each project is broken down into step-projects lasting no more than 10 weeks. Note that each step-project is an experiment that tests an idea using the Build-Measure-Learn principle. This helps teams avoid wasting resources on pointless projects.
  4. Tasks. Projects are broken down into step-projects, and step-projects are broken down into tasks that many agile practitioners will be familiar with. As a result, this block of GIST Planning does not need to change. What’s important is that the blocks above it can also behave in a somewhat agile manner.

Advantages and disadvantages of GIST Planning

GIST Planning is mostly based on agile principles, but it does have some clear and unique advantages for businesses.


  • Continual generation, evaluation, and prioritization of ideas. In GIST Planning, there is no potential for one bad idea (followed without due diligence) to stymie 5 great ideas. With less emphasis on the arbitrary scheduling of ideas, businesses continually cycle through ideas to find the hidden gold. 
  • Goal-driven development. A key tenet of GIST Planning is the stipulation that ideas must further company goals. This allows decision makers to devote resources to company wide initiatives that deliver on mission or purpose-related goals.


  • Short-sightedness. The incremental and iterative nature of GIST Planning means that a business cannot commit to goals beyond a few months into the future. This compromises the ability of the organization to set goals for large projects that may take years to materialise. Ultimately, future resource planning and allocation become vague and uncertain, potentially hindering growth and agility while also making the company more reactive.

Key takeaways:

  • GIST Planning is an agile approach to project planning based on the principles of lean start-up and agile development. It favours team autonomy and velocity through a reduced management presence.
  • GIST Planning is based on four blocks that encompass a planning methodology: goals, ideas, step-projects, and tasks. Each block runs concurrently with a specific planning horizon and frequency of change.
  • GIST Planning advocates the continuous generation and evaluation of idea. This helps project teams avoid sinking time and money into projects that turn out to be unviable. However, businesses that adopt GIST Planning may have trouble implementing large projects that require a commitment lasting more than a few months.

Related Agile Business Frameworks


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.

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 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 (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 (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.

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.

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

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

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 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

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 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 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.

Lean 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

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 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

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) 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

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

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 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 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.

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@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.

Read Next: MVP, Lean Canvas, Scrum, Design Thinking, VTDF Framework.

Read More: Business Models

Read Next: Business AnalysisCompetitor Analysis, Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Main Free Guides:

Scroll to Top