Prioritize Strategy Over Tasks Before the Week Fills Up
Prioritize strategy over tasks by writing one sentence the studio will not violate this month, and only then writing the deliveries. The sentence is a choice about the work you will refuse. The tasks are the files that serve that choice. This page is that order of operations for a design founder. It does not promise growth, a better hit rate, or a calmer week. It is not legal, financial, or management advice.
The weekly lists on the small business ceo time management page still hold Decide, Make, and Check. Handoffs still use the founders delegate effectively note. Capture still follows the getting things done method and the five steps at gettingthingsdone.com. None of those lists choose what the studio is for. This page is that choice, written small enough to use.
A sentence, not a deck
Write one sentence in the form “This month we will ship X and we will not take Y.” X is a kind of delivery you can point at. Y is a kind of request you will decline or delay. If the sentence has no “will not,” it is a wish, and wishes do not sort a task list. If X is “quality” or “growth,” it is not a strategy line yet. Name the work.
Put the sentence where Monday’s list starts. Do not hide it in a deck. A deck is a task that feels like direction. The sentence is the direction. People should be able to read it without opening a file.
You will want a second sentence. Wait. Two strategies is how every request fits somewhere. One refusal is the part that makes the list shorter. Add a second line only after the first has survived a week of real asks.
How to prioritize strategy over tasks on Monday
Read the sentence before you read the tasks. For each task already on the list, ask whether it ships X or sneaks in Y. A task that ships X stays, and it still needs an outcome, a limit, and a done line. A task that is Y moves off this week’s list, even if it is easy and even if someone already started a file. A task you cannot classify is a decision, not a delivery. It goes on Decide until the sentence can see it.
Do this with the live work, not with a sample. A homepage for the offer you named is X. A side illustration for a request you said you would not take is Y, even if the illustration would look good in a portfolio. The portfolio is not the sentence. If you want the portfolio piece, change the sentence on purpose and tell the studio. Do not keep the sentence and do the work anyway. That teaches people the sentence is decoration.
New mail does not skip the sentence. A flattering request is still Y if it matches the refusal. Reply with the refusal in one line, and do not open a file “just to see.” Seeing is the start of a task. The task will ask for a check later, and the week you protected will be gone.
Tasks stay concrete
Strategy does not replace the task. It decides which tasks exist. A task that survives still looks like a file: “send the two hero options,” not “advance the brand.” The person doing it should not need the strategy deck to know what done is. They need the sentence only when a new request tries to widen the file. Then they can say the request is Y and stop, instead of absorbing it to be helpful.
Helpful absorption is how strategy loses to tasks. Someone adds a section because the client mentioned it. The section is reasonable. It was also the thing the sentence refused, or it was never in X. Write the addition down as its own ask. If it is a change to the sentence, you make that change in the open. If it is not, it waits. Quiet additions are tasks that outrank the sentence without anyone deciding they should.
Keep the done line narrower than the sentence. The sentence is the month. The done line is this file. A file that tries to express the whole sentence will not finish. Ship the piece of X this file was for. Leave the rest of X as later tasks that still pass the same test.
When the sentence is wrong
A sentence can be wrong. A client you refused might be the work you actually want. A delivery you named might be too big for the people you have. Change the sentence in writing, on the same page as the list, and say what moved. Then re-sort the tasks. Do not keep the old sentence on the wall while the list does something else. Two stories is worse than a missing story, because people will quote the one that approves their task.
Review the sentence when the month’s X is shipped or when Y keeps winning. If Y keeps winning, you do not have a discipline problem. You have a sentence you do not believe. Replace it with the refusal you will actually say out loud. A strategy you will not say to a client is a private preference, and private preferences do not sort a shared list.
Do not score the week by how many tasks closed. A long list of finished Y is a busy failure. A short list of finished X is the point. This page will not give you a ratio, a benchmark, or a claim about what finished work is worth. The record is the sentence and the tasks that were allowed to exist under it.
What not to add
Do not add a strategy workshop, a new board, or a scorecard to prioritize strategy over tasks. The sentence and the Monday sort are the practice. A workshop that does not change the sentence is a task wearing a serious name. A board that duplicates the list is another home for the same work. A scorecard that counts tasks will pull you back toward the thing this page is trying to put second.
Do not delegate the sentence. Someone else can draft options for what X and Y might be. The choice is yours if you are the person who must tell a client no. Handing off the no, without the sentence, is how a teammate either hides or over-refuses. Say the sentence. Let them refuse from it.
Tomorrow, write the sentence at the top of the list you already use. Cross off one task that is Y. Start one task that is X. Leave the rest unsorted until that first file moves. Prioritize strategy over tasks in that order, or the tasks will set the strategy by the end of the morning.
If you share the studio, read the sentence aloud once. Ask which current file would fail it. Fix that file’s place on the list before you talk about new work. Agreement about a future offer is cheap. Agreement about a file already in progress is the test. If the room cannot name the file, the sentence is still too soft to use.
Keep a single old copy of the sentence when you change it, with the date, so you can see what you refused last month. Do not keep a museum of every version in the task tool. One previous line is enough to stop a quiet return of Y. More than that and you are curating strategy instead of shipping X.
Use the sentence on a proposal before you use it on a pixel. A proposal is a stack of tasks waiting for a yes. If the proposal is Y, do not spend a Make block making it beautiful. Send the refusal, or rewrite the sentence first. Polishing a proposal you intend to decline is the most respectable way to let tasks outrank the month. The client cannot see your sentence. They can see the draft you sent, and a draft is a yes wearing layout.
When a teammate brings a task they love that fails the sentence, thank them for the file and park it. Parking is a named place, not a vague later. Write “not this month” on the line and the reason in the words of Y. They can argue for a sentence change. They should not argue for a quiet exception. Exceptions are how a strategy becomes a slogan by Friday. One exception you record in the sentence is a change. One exception you allow in chat is a leak.
At the Friday close, read the finished files against the sentence and ignore the unfinished ones for a moment. Finished work that is not X is information. It tells you the sentence lost. You do not need a chart to see it. Write what won, in a line, under the sentence. Next Monday the sort starts from that evidence, not from how busy the calendar felt. Busy is a task count. The sentence is the filter you said you wanted when you chose to prioritize strategy over tasks.
If the month ends and X is not shipped, do not write a longer sentence to hide it. Shrink X to the delivery that is still true, or move the unshipped part out of the sentence so the list stops pretending. A strategy line that contains work you will not touch is a task list in disguise. Cut it until every part of X has a file with a done line, or until the part without a file is gone. Then the remaining tasks are allowed to be small, ordinary, and finishable.
