“A good plan violently executed now is better than a perfect plan next week.” – George Patton

“Once I have X, I can do Y.”

This phrase is the defining characteristic of the toolbox fallacy: thinking you can’t do something until you have the right tool.

The toolbox fallacy is self-deception disguised as excuses or a lack of “tools”. The issue with these tools is that you believe that you need them and thus, can’t (or won’t) start a project without them.

“As soon as my Apple Watch arrives, I’ll start training for the 5K.”

The problem is when X arrives, do you crack on and get started with the Y? Often times, it’s too easy to continue down the slippery slope of toolbox logic.

“My Apple Watch arrived, but now I need a coaching app – which I am yet to have downloaded.”

So, how do you overcome the toolbox fallacy? Simple: You default to action. In other words, you get the ball rolling – whether you have all the tools you think you need or not.

The solution, in a sense, is to be more agile.

In this post I’ll be looking at how to overcome the toolbox fallacy by putting the systems in place to move fast, and with virtue. I’ll try to address:

• How do you plan and structure clear action items, so you can move fast and be sure you’re making the right decisions?
• How will you move fast without breaking things (by things I mean humans)?

And, to sum things up I’ll take a look at how we at Process Street use OKRs to decide when it is we should be moving fast vs when we should be slowing down.

To jump to a specific section click the appropriate links below:

• Toolbox fallacy: Once I have X, I can do Y
• Moving fast with the toolbox fallacy
• A framework to move fast (& with virtue)
• How our OKRs help us avoid the toolbox fallacy

Let’s start by unpacking the toolbox fallacy in more depth! 🛠
Continue Reading

From sprints to cycles, and from product backlogs to …well…no backlog at all. These are just a couple of examples of the differences between Shape Up and agile approaches such as Scrum.

But, what exactly is Shape Up? How does it, when put into practice, differ from Scrum?

Our development team here at Process Street recently made the move from Scrum to Shape Up and I asked them how the two compare. This post outlines the key takeaways from the team and takes a closer look at what Shape Up is as a whole.

To jump to a specific section, click the appropriate link below:

• A re-cap on the Scrum workflow
• What is Shape Up?
• How does Shape Up work?
• Scrum vs Shape Up
• Shape Up at Process Street
• Key takeaways: From Scrum to Shape Up

Alternatively, to read the whole post – just keep on scrolling. 🚀
Continue Reading

Once upon a time, the island nation of Sri Lanka was called “Serendip,” a word derived from Sanskrit which means Dwelling-Place-of-Lions. (Lovely, right?).

Serendip provides the setting for the Persian fairy tale “The Three Princes of Serendip”, who throughout their travels, stumbled upon an uncanny amount of luck. 🤴🏾🤴🏾🤴🏾

The story of the princes and their relationship with luck is where the wonderful word Serendipity comes from. Serendipity, meaning accidental, unexpected, random, wonderful, happy, luck.

It is luck, or rather, how to make your own luck, that is the focus of this Process Street blog.

This post embraces and explains tech entrepreneur Jason Robert’s concept of “Luck Surface Area”, in the hope of helping you, the reader, increase your luck both in life and in business.

To jump to a specific section of the post click the appropriate link below. Alternatively, just keep scrolling to learn about the three lucky princes, Luck Surface Area, and how you can make your own luck.

• Serendipity and making your own luck
• How to make your own luck
• Make your own luck: The Luck Surface Area equation
• 5 actionable ways you can increase your luck surface area and make your own luck

Feelin’ lucky? ✨

Let’s get started.

Continue Reading

According to a survey performed by KPMG and Forrester only 34% of decision-makers say they feel confident in their data …

A sad state of affairs.

Fortunately for the 66% of decision-makers who cannot rely upon their data, there is an answer *drum roll please* . . . the Enlightenment . . . of data.✨

Who would’ve known a school of thought that revolutionized the 17th and 18th centuries could be harvested to optimize our present-day data management?

“The Enlightenment included a range of ideas centered on the sovereignty of reason.” Dorinda Outram, Panorama of the Enlightenment

Governed by a philosophy of rationality the Age of Enlightenment (also known as the Age of Reason) made decisions based upon a single source of power or primary source of knowledge. The source of truth and knowledge in this instance was determined by the senses.

Single Source of Truth or SSOT, the focus of this Process Street blog post, also takes the sovereign approach.

However, rather than the senses, the sovereign power for SSOT is a reliance on un-replicated, autonomous, self-contained, and enhanced data.

To find out more about SSOT and how it can enlighten your data processes, keep reading.

Alternatively, to jump to a specific section of the post, click the appropriate link below.

• The path to Data Enlightenment
• ‎What is Single Source of Truth
• The role of data for Single Source of Truth
• ‎How to obtain a Single Source of Truth
• ‎Single Source of Truth in practice
• ‎Single Source of Truth is Data Enlightenment

Continue Reading

I once lost $45,000.

What makes it worse (or perhaps better?!) is that it wasn’t my money.

It was my previous employer’s.

I was managing a website build for a big client and was under huge pressure to meet a tight deadline. So, as many do, I decided to start the project before the Statement of Work (SoW) was signed by the client.

This was a big, expensive, mistake to make.

It cost an additional $45,000 to re-work parts of the build that the client had verbally approved, but hadn’t legally signed off.

Ouch.

(Despite what you might think, this isn’t the reason I don’t work there anymore!)

According to research, 37% of projects fail due to a lack of defined and approved project goals and objectives, which come with a Statement of Work (SoW). This causes around 80% of organizations to spend at least half their time on expensive rework.

“Not using a Statement of Work – SOW during the project initiation is a major cause of project failure” – 4PM, Statement of Work – SOW

But what is a Statement of Work (SoW) and how do you create one?

All will be revealed in this Process Street post, as we go through:

• What a Statement of Work (SoW) is
• Why bother with a Statement of Work (SoW)
• How to create a Statement of Work (SoW)

If you’re in a hurry, grab this free Statement of Work Process Template now, and catch up with the rest of the post when you can:

Click here to access the Statement of Work (SoW) Process Template!

Otherwise, keep reading and we’ll go through this template, in a little more detail, later.

Let’s get into it!

Continue Reading

This is a guest post written by Ashley Ferro, a freelance content writer & copywriter specializing in SEO content marketing.

There’s nothing more frustrating to a project manager than witnessing the slow, painful death of a healthy project to the beast known as scope creep. When last minute changes transform their straightforward, A-to-B project plan into a sprawling mess of up-ended sprint plans and gold-plated feature requests, branching out in all directions with no concern for time or resources.

In one extreme example, the head contractor for the extension of a city library ended up actually suing their client in a scope-creep induced rage, claiming that their almost 55-week delay was a direct result of the large number of last minute changes.

In order for a project to be successfully completed on time, the project manager and their team need to agree on a clearly defined project scope before getting started.

However, life isn’t so straight forward and changes to the project will inevitably need to happen.

But additional problems can arise if the changes aren’t dealt with properly.

Scope creep can quietly sneak its way into your project and set your team down an unproductive and self-destructive path, wasting your company’s resources, missing deadlines, weakening team communication and, ultimately, ruining any chance of your project’s success.

So what can you do to avoid this fate, and overcome scope creep once and for all?

In this Process Street article, we’ll be covering everything you need to know scope creep–from what (and who) causes it, to how to manage it, even in an agile environment where change is embraced.

We’ll be covering:

• What is scope creep?
• How different stakeholders can contribute to scope creep
• What are some common causes of scope creep?
• Most effective ways to manage scope creep
• What we can learn from Agile to prevent scope creep?
• Using Process Street to avoid scope creep
• Additional project management resources

If, however, you’re struggling with planning your own projects and want a quick solution, grab our free Project Request Form Template below!

So, let’s get started with the basics!

507 blog posts.

That’s how many items our team has created, edited, and published since implementing Scrumban.

Before we set up our system, we were mostly scrabbling to get items together from week-to-week, without knowing what we’d be working on next.

Now, we’re always 3 weeks ahead of our publishing calendar, have built our blog to over 130,000 subscribers, and have expanded our team by over 300%.

That’s why we here at Process Street will take you through this (practically new) method for managing your team and projects.

We’ll cover:

• The basics of Scrumban
• The pros and cons of Scrumban
• How to implement Scrumban

If you want a sneak preview of how we’ve deployed Scrumban, I’ll give you a hint. It’s got something to do with the Sprint Planning checklist below (which you can grab for free!)…

Let’s get started!
Continue Reading

You’ve heard of the moonwalk. But have you heard of the Gemba Walk?

From a business standpoint, the Gemba Walk is infinitely more useful (though the moonwalk is pretty cool).

Specifically, the Gemba Walk allows businesses to continuously improve how they do things by remedying their processes, procedures, and workflows for recurring tasks. The continual process improvements that Gemba Walking brings helps businesses exponentially – 1 in 4 improvements save time, and 1 in 10 improvements save money.

And this is all achieved by simply stepping back, rather than blindly pushing forward.

Want to know more?

I thought so.

In this post, I’ll tell you what Gemba Walk means, the origins of it, its benefits, and how Process Street can help both remote and physical businesses do the Gemba Walk.

Just read through the following sections to get clued up:

• What is a Gemba Walk?
• The origin of Gemba Walks
• The 3 elements of a Gemba Walk
• The benefits of Gemba Walks (& lean management)
• Undergoing process improvement with Process Street!

Now, let’s sprint through the rest of the post! 🏃‍♂️

Continue Reading

“Ladies and gentlemen, this is your captain speaking. We have a small problem. All four engines have stopped.” – Eric Moody, British Airways Captain, Business Insider

The words no one wants to hear when they’re tightly strapped into an aluminum tube, flying at 900kph, 35,000 feet up in the air.

One in three Americans either feels anxious or scared to fly and 73% are fearful of mechanical problems during flight.

“On a flight from Kiev to Toronto, several screws fell out of the ceiling onto my lap…When air started sucking out of a loose seam around my window, I really started to panic.” – Nate Drescher, The Travel

But air travel in the United States is the safest in the world. The odds of dying in a car accident are about one in 5,000. The odds of dying in a plane crash are about one in 11,000,000.

So, putting our fears aside for a second, why is flying the safest way to travel?

Well, partly because of the advances in aircraft design, technology, and engineering, but mostly because of Aerospace Standard (AS) 9100. The International Quality Management System standard for the Aviation, Space, and Defense industry.

“A person would have to fly on average once a day every day for 22,000 years before they would die in a U.S. commercial airplane accident” – Dr. Arnold Barnett, FlyFright

Whether you’re an avid flyer, an aviation expert, or an aerospace supplier, join me as we fly through the following AS9100 topics:

• What is AS9100 and where on earth did it come from?
• The 5 orbital differences between AS9100 and ISO 9001
• AS9100 certification, it’s not rocket science
• AS9100 and Process Street: The sky’s the limit

Fix your seat in an upright position, fasten your seatbelt, and prepare for take-off…

Continue Reading

Bread. Beer. Bacon. *Homer Simpson voice* Mmm, bacon…

No matter what tasty food product your business is creating (or helping to create), a robust food safety management system is essential.

Why?

Because without one, you could be exposing your food to risks and hazards that are both life-threatening for your consumers (420,000 people die each year due to contaminated foods), and business-destroying for you. Plus, by not having a food safety management system in place, you’ll lose pivotal trade opportunities with others in the food industry.

To ensure you have a food safety management system in place – and that it’s up to scratch – there’s FSSC 22000.

In this post, you’ll discover what FSSC 22000 actually is, why it’s so important, how a GFSI recognized certification will benefit you, and how Process Street can help with it all.

Make your way through the following sections to get clued up:

• What is FSSC 22000?
• What’s the difference?: FSSC 22000 vs ISO 22000
• What a GFSI recognized certification means for you
• The additional positives of FSSC 22000 certification
• Achieve FSSC 22000 certification with Process Street!

Now, it’s time to taco about FSSC 22000 and food safety! 🌮

Continue Reading