Who Does the Work, With What, and How Many Revisions

The case’s constraint overlaps our job. The owner relaxes and asks who will do it. The answer comes. “The team will handle it.” The slide has several faces. No hand is holding the file.

The last piece said to ask, inside the case, which role they held. On our job that question becomes present tense. Who makes the file, who gathers the comments, who speaks last. People who hire well split the noun “team” into roles. A noun alone makes the schedule a guess.

The schedule shows up only when the roles show up

A project has someone who makes, someone who reviews, and someone who approves. Tie the three into one name, and mail goes to the team while the answer is late as a person. The seat of the lateness is invisible.

There is no need to collect many names. Split the roles into one line each. Planning, design, build, content, coordination. Each line has an end of responsibility. Without an end, the role is attendance. Attendance does not make a file.

If an outside person joins, write the stage on that line. Which days of shooting, which cell of the build, the handover of print. Without a stage, the outside hides inside the team. A hidden outside becomes the subcontract of the next piece. Write it now, and later is not a surprise.

People who hire well also write the final approver. If the person who makes and the person who closes are different, revision lives between them. If the closer is empty, “the team will look” becomes the reply. A revision with no reply is not counted as a round.

A tool is not a rank. It is where the file lives

Which program they use is not a score of skill. Scoring sends the room into taste. What to see in a tool is a place. Where the file is reviewed, where versions stay, and in what format the last source is handed over.

If review happens only as chat images, comments disappear easily. If versions live only in a personal folder, context stops the day the person changes. If the source format is unset, the last day leaves only web files.

People who hire well do not take a tool’s name as a boast on the contract. They take it as the path the file walks. One sentence of path is enough. If the sentence is a brand description, it is not a path yet.

Our tool gets written too. If we cannot open the design file, review needs another format. Leave that format unset in the meeting, and the proof arrives as a link that will not open. A link that will not open delays the reply.

A revision count needs an object

“Two rounds of revision” looks clear, like a number. Without an object, the number is a different job to two people. One side means the direction of a proof. The other means typos. The same two eats different weeks.

The object can be split. Proof, copy, build defects. A new feature does not go inside that count. The moment it does, revision becomes another name for a scope change. If a scope change hides inside the count, the quote’s total moves quietly.

Beside the count, one round needs a definition. Is one round the whole screen, or the items that were pointed at. Without a definition, the second mail swallows the first round. People who hire well, before turning “we will revise enough” into a count, write what is being counted.

Typos inside a review window and a proof whose direction changes are different clocks. Put typos inside the proof count, and the direction change disappears. Put direction inside the typos, and fixing letters becomes the project. One line that splits the clocks keeps the schedule.

A slide with no hands

Six faces, and the room relaxes. The relief is a headcount. A headcount does not open a file. The hand that sends the proof on Monday, the hand that gathers comments on Wednesday, the hand that writes pass on Friday. If those three hands stack on one person, six faces are waiting.

People who hire well write the week beside the slide. The hand of week one, the hand of week two. A week with no hand is either outside, or a week waiting for our reply. Both can be said now. Unsaid, that week becomes “the team is looking.” Looking is not a cell on the schedule.

The revision count follows the hands too. If the hand that draws the proof and the hand that fixes copy differ, one number lets one hand eat the other hand’s week. The eaten week is not on the quote. Absent, it is later described as a question of diligence. It was not diligence. The object was never split.

When the hand that hands over the source is written, the scene closes. If that hand is a partner, the format and the moment have to become a sentence of our contact. If they do not, on the last day the folder sits in the partner’s cloud. The owner of that cloud was not on the slide. If an owner who was not there holds the file, the team is still “in progress.”

How a count eats a week

A proof arrives Wednesday. Thursday we send that the direction is different. Friday we fix the copy. Next Monday we ask for one more button. The vendor counts the three as one round. We count the three as three. Both of us are reading the quote’s “two rounds.” The same number is a different week.

People who hire well write the definition of a bundle beside the count. One round is the direction of one screen. Copy and typos live in the review window. A new button is outside the count. Without that definition, Monday’s button swallows Wednesday’s direction. After the swallow there is no round left, and the next revision is an extra quote. The reason for the extra is not new work. The counting method differed.

Write the hands together, and the definition stops wobbling. If the hand that draws direction and the hand that fixes words differ, do not call both hands with one mail. Put two hands in one mail, and the count becomes one hand. A count that became one hand calls the team again. A count that returned to the team looks like the first slide. Faces, and no file.

The next question is polite only when the scene exists

Owner, the path of the tool, the object of revision, the format of the source. With those four lines, “the team will handle it” becomes a scene. With a scene, the schedule is the sum of roles. When the sum is visible, an empty role shows up as a risk.

If the empty role is outside, the next question is natural. How far does that person go, and who speaks if they are late. Ask about subcontracting before asking about the scene, and the question sounds like suspicion. See the scene first, and subcontracting becomes a structure.

People who hire well do not relax at the size of the team. Size lives on a slide. The file lives in a hand. When the hand is written, the revision count follows the hand. Without a hand, the count stays a promise of the team, and the promise is swallowed by the week.

If these four lines are only spoken in the meeting, three days later only the air remains. So the piece after next is about writing them down. Before that, ask politely about the outside and the delay hiding inside the scene. That is the next piece.