Before you go dark on a client again, read this…
How to make yourself more valuable by stopping feature bloat
It’s human nature. There’s was a point in the project where progress stopped — a rabbit hole appeared, a feature bloated out of control, communication tired — and suddenly my two very experienced friends had blown their budget and deadline.
Disclaimer: This is a complex problem. I’m not claiming I have all the answers. But even though nothing I say in this article can magically solve the issues for you… I’m going to let you in on a secret. Even if you stopped freelancing forever, these problems wouldn’t go away.
In fact, I still battle them daily in my business. Everyone does.
So, how can we improve the projects we work on?
- Stop jumping into rabbit holes immediately when you find them.
When you’re about to spend 3 hours on something you initially thought was going to be take 30 minutes — stop. That’s when you need to ask yourself if what you’re doing is really worth it. Skip the rabbit hole and look for a solution that takes 20% of the time but delivers 80% of the results.
- Work on the the most important things first.
I’ve been known to get lost in details before I have the basics in place. This puts me in a bad position once a deadline approaches because I’m stuck. If I had started with the most important part of the project, I’d be in a position to trim some of the other stuff and still ship a functioning project. Speaking of which…
- Cut the scope down!
I’ve never regretted cutting unessential features out of a project. Focusing 100% on what truly matters will lead you to build a strong foundation of profitability for both you and your clients.
- Be on time, no matter what.
I got this rule from Jason Fried. He says you should have a hard timeline but soft scope. That way, the people you work with can trust that you’ll deliver on what you say. Use scope cutting to gain that trust.
- Focus on the project before the project.
This is always a bigger deal than I realize. Implementation is the thing I focus on but always ends up being the smallest part of a project. Instead do yourself a favor and focus on carefully laying out the project before you dive in. Think deeply about timeline, features, number of people, and monetary investment before I start.
- Bake in 30% more than you need for “unexpected” emergencies.
Let me spoil the ending of your next project. Something “unexpected” will happen — and it’ll make the project take longer than you thought. I use quotes around unexpected because it’s really not unexpected. It happens in every. single. project. With those odds you can guarantee you look like a wizard.
What’s the best way to implement all of these? Here’s what I’m doing…
I’m building a template (in Basecamp) that I’m going to use to anticipate problems on future projects. Once it’s done I’m going to share it with my email list.
Want to hop on the list that gets notified once my template is ready?
(There’s a secret bonus you get when you sign up too).