When it really comes down to it, almost everything we do in our work boils down to solving problems.

Solving problems for other people, for our teams, for ourselves.

Problems, problems, problems, everywhere we look.

Given that this is our reality, it helps to have a framework before we begin to work on a given problem to determine how to best go about attempting to solve it, and indeed if we should even be the ones working on it in the first place.

Before accepting any project, or beginning to solve any problem we should ask ourselves 3 questions to help calibrate our view of what needs to happen and how it needs to be done.

Who is it for?

Most of us are not in the business of mass-market product or service manufacturing.

Who we are doing the work for, be that our audience, a client, a client’s audience, or anyone else will have a huge effect on the final product.

Designing a new website for Nike is not going to look the same as designing a new website for Ford, let alone designing a website for the new podcast you’re launching for your own audience.

Too often we think we’re making something for a client, when we’re really making it for their audience.

We need to dig deeper, because who it’s really for matters.

What’s it for?

At the start of a new project, especially one we’re excited about, it can be easy to get ahead of ourselves and dive in headfirst without taking the time to ask what the bigger purpose is behind it.

Sometimes the reason is obvious, such as building a landing page with the sole purpose of selling a product, but it isn’t always so clear.

When it comes to the website for your podcast, for example, there’s a lot to consider.

You may be launching the podcast to educate your audience, build a loyal following for yourself, create and sell products and services, level up your network by connecting with interesting guests, and build up clout in your industry.

How will the website serve each of those goals? A website that focuses only on one of those goals will be a lot different than one that supports all of them.

Why Am I Doing It?

The first side of this question addresses whether you should actually be the person doing this project.

It’s more than likely on any number of potential problems that you get invited to solve that you may not be the best person to take it on.

Knowing that you’re not the ideal choice and taking on the project regardless has a way of backfiring, if not in the form of failed or underwhelming project results, then in the form of intense periods of stress while trying to keep your head above water on a project you’re ill-equipped for.

Part of doing work that people rave about is knowing your strengths and capabilities and operating within them.

This question takes on additional meaning when it’s not just you doing the work.

As our team at Counterweight Creative has grown, I’ve been finding myself asking this question more and more about tasks I’ve always done but should perhaps no longer be doing.

Every month I look at my time tracking report and for each task-category ask myself why I am the person handling that task.

Sometimes it’s because I’m the only one who has the skills, knowledge, or relationships to do it.

But sometimes it’s habit, fear of handing it off, or because I just haven’t created the training resources and structure to hand it off.

Regardless of what the reason is, it’s essential to be aware of it.

If you’ve decided that you are the person to be taking on a project, this question can be asked from an additional angle as well.

Why am I DOING it?

In a perfect world, every project we took, every problem we solved would be in the service of changing the world for the better, and the impact of our work would be obvious.

But let’s not kid ourselves. There are a lot of reasons that we might agree to solve a problem, either for someone else or for ourselves.

Sometimes we do take on projects that we believe deeply in with an obvious impact.

Even when that’s the case, money usually plays some factor in our decision to sign on.

Some projects we take on only for the money.

Others we forgo money entirely either to give back or to gain experience or skill.

There are no universal “wrong” reasons to do the work you do, just so long as you’re clear on why you’re doing it.

Remind yourself that if the only reason you’re doing a project is for the paycheque, it may not be worth getting as emotionally attached to the work, especially when the client starts making meaningless revisions that reduce the value of your contributions.

I’m not saying to detach yourself from your work entirely.

Care about the work you do. Care deeply and fight for it when you need to.

But understand which projects are worth the extra energy of championing and fighting over, and which you’re better letting go and moving on from.

Knowing why you’re doing the work will help you maintain the appropriate temperament, make the work more enjoyable, and keep you sane.

Revisit These Questions Regularly

While it’s essential to ask these questions and get clear on your reasoning before beginning on a project, it’s equally important to build a habit of revisiting these questions at regular intervals throughout the project.

This keeps you on track, making decisions that serve the audience and the goal of the project and helps ensure you’re doing your best work, which when it comes down to it, is solving problems in the most appropriate way possible.