Before you start the next project, think about the conditions of satisfaction.
What does that mean? That means that whoever it was that gave you a project probably has some idea about what they want to have done with it; they have an outcome in mind.
They also know what procedures have been followed in the past.
They know where things can go wrong, what you should be managing around, and when this thing is due, and what “done” looks like.
By getting the conditions of satisfaction before starting a project, your likelihood of having to do it only once AND having somebody give you a high-five at the end goes up substantially.
Sadly, here’s how it works for most people:
- they hear there’s something to be done
- they start running wildly toward that direction, not understanding…
- the when
- the how
- the goal, what the outcome is supposed to look like…
And then, when they deliver something to their boss— or worse yet, have it sitting on their desk or in a folder on their computer, that is NOT a recipe for getting things done.
When we don’t find out the conditions of satisfaction first and then come back afterward and ask, “Did this meet the conditions of satisfaction?” What we’re doing is creating chaos in the workplace.
Listen, nobody needs to be working nights and weekends doing rework— not you and especially not your boss, because if they keep having to do your work over again, likely that does not bode well for your career. So, every time you’re given instructions about what to do, first just stop.
Ask a lot of questions to get the conditions of satisfaction before moving ahead.
But move quickly once you have them and bring it back and ask if this meets the conditions of satisfaction.