There are a number of frameworks we use regularly to help effectively manage projects. One such framework is what we call, “Five to Seven”.

The “Five to Seven” framework is essentially the simple idea that most processes can and should be explained in five to seven steps. An overall process should be explained in five to seven steps. A process step can and should be explained in five to seven sub-steps. A problem can be solved in five to seven steps. A project can be completed in five to seven steps. A vendor can be selected in five to seven steps. An approach can be explained in five to seven steps. You get the picture.

This isn’t a hard-written rule. If something can be easily explained and well understood in four steps, then that is absolutely the right thing to do. Sometimes three steps are completely appropriate. But “Five to Seven” is our starting point. At Project Outlier, we have found that “Five to Seven” usually provides enough detail so people at all levels understand yet not so much information that everyone gets lost or stuck in the details.

Here are two real life “Five to Seven” examples from recent client engagements.

One of our clients needed to migrate data from numerous source systems into a SaaS platform. We worked with the client to understand the fairly generic challenge within their specific context. Then we outlined a five step approach to deliver a solution that included:

  1. Defining the migration requirements and business rules,
  2. Cleansing the source data,
  3. Migrating the data,
  4. Verifying the migrated data, and
  5. Completing post-migration tasks.

A different client struggled to collaborate across internal business units when responding to strategic business development opportunities. We laid out a straightforward approach to address their challenges:

  1. Document the current processes (Note: each business unit had their own processes!),
  2. Assess the current processes,
  3. Recommend process improvements,
  4. Prioritize and select the improvements to be implemented,
  5. Implement the prioritized improvements, and
  6. Evaluate the results.

“Five to Seven” is particularly helpful when facing complex situations. Yet it’s also potent when one’s natural instinct is to “just do it”. When facing a problem, people often want to just solve the problem. Yet “Five to Seven” is a great framework to ensure that the right problem is solved.

So instead of:

  1. Solve the problem (essentially, “Ready? Fire!”)

try:

  1. Define the problem,
  2. Determine the underlying cause or causes of the problem,
  3. Identify and select options to solve the underlying cause or causes,
  4. Implement the selected option(s),
  5. Confirm that the problem has been solved.

What we and our clients love about the “Five to Seven” framework is that it helps get and keep the entire project team and all stakeholders on the same page. And when everyone is on the same page, the odds of completing projects on-time, within budget, and with high quality skyrocket!

Here is a cleansed version of our first example. As you can see, the overall approach includes five steps. Then, each primary step includes five-to-seven key activities (aka sub-steps).

How to migrate LMS data in five steps

Try the “Five to Seven” process framework in your workplace. We are confident that it will help you more effectively convey complex subject matter to a variety of audiences. If you find this framework to be helpful, we’d love to hear about it!