Whether you’ve completed a project a hundred times before or you’re faced with a new challenge, having some kind of formal project request form prevents the whole operation descending into a game of broken telephone and wasted resources.

No matter how good your team’s discipline, if all they have to go on when you request a project is a vague message and their memory of the requirements, sooner or later you’re going to have a problem. Either a project will be started which won’t be worth your time or your instructions will be lost in the trickle down to those taking action.

‘Whilst on manoeuvers, a brigadier commanding a certain brigade stationed in Aldershot passed the word to the nearest colonel to him:

“Enemy advancing from the left flank. Send reinforcements.”

By the time it reached the end of the right flank the message was received:

“Enemy advancing with ham-shanks. Send three and fourpence!”’ – Garson O’Tool, relaying a real-world instance of broken telephone from 1914

Continue Reading

According to Atlassian, unnecessary meetings cost the US economy $37b a year in wasted salary costs.

In fact, per the same study, half of all meetings are considered “wasted time”.

What differentiates a successful meeting from a failed one? How do we make sure our meetings are consistently successful?

In this article, we’ll discuss the fundamentals of how to run a successful meeting; the 7 key steps advocated by MIT professor Neal Hartman.

And we’ll share with you our internal method for running meetings in a structured manner with Process Street.

Continue Reading