When you’re working on a development project for a client, it’s often pretty easy to figure out when you’re all done with it.
After all, you did a requirements document before you started, right? So you know you’re done when the requirements are all met, and the client is happy. Easy peasy.
But on a design project, it’s not always so easy. There’s always something more you could tweak. One more adjustment to that logo, one more look at the spacing on that text. Where does it all end?
Well, on projects where we work by the hour, we usually apply what we call the 90-10 rule. If the last 10% of minor fiddling is going to take lots of time and be virtually invisible to the client, we stop at 90%. Then, when we show options to the client for feedback, we review what additional things we could do (and how much time they’d take). That way, the decision is the client’s.
But on projects where we have a flat fee, it’s a little tougher. At some point, there’s a diminishing return, but when you’re immersed in a project, it can be difficult to see it. So as designs are nearing the end stages (before getting final client sign-off), we do an internal review, and have a discussion about what’s where, and what could still be done, and figure out if it makes any sense.
These discussions are often spirited, and also often lead to great design outcomes. We do it on the dev side, too, but usually earlier in the product cycle.
It can be difficult when you’re head is down on a project to see that you’re done. That’s why we rely on others to help.