← BACK TO THE BLOG

Project scope

Getting halfway through something and then realising it’s not the direction you wanted to take is never fun. It’s even worse when it’s a client project.

A lot of the time this can be avoided by creating a basic project scope at the start. I’m not talking a 30-page project brief. Just a basic outline of the project.

Knowing what you’re trying to achieve and clarifying your ideas of how you’re going to achieve it will suffice in most cases.

I like to create a 1-page project summary with all of my initial thoughts on a project. I’ll outline my objectives with the project, initial ideas, marketing thoughts, ideal customers, technical requirements, possible challenges that may arise, important things I need to research etc.

Whenever I’m working on a project, I’ll refer back to this project scope summary. If need be, I’ll review and update it if I feel things really need to change.

Shane Black
WRITTEN BY Shane Black.

Twenty-odd years running hands-on businesses, including a stone and fabrication shop. Now builds practical AI systems for owners on the Gold Coast, and writes up what works as he goes.

Keep reading.

All posts →