Your work isn’t finished until your colleagues have seen it
A piece of work isn’t “done” the moment you finish it — it’s done once the people around you have looked at it and quietly signed off. Quality isn’t yours to declare alone. Expect to share drafts early, check in partway through, and run things past your boss and the relevant colleagues before you call anything complete. This isn’t distrust or micromanagement; work is treated as the group’s product, not your personal one, so completion is a shared judgment. The common misstep is going quiet, perfecting something privately, and presenting it finished with a flourish — which reads as having cut everyone out. Keep the work visible and provisional as you go. Something that has been circulated, discussed, and absorbed by the team is what “good work” actually means here.
The first draft is supposed to come back covered in red
Don’t be alarmed when work you’re proud of comes back marked up with corrections and little or no praise. That’s the normal path, not a verdict on your ability. Good work is reached by iterating toward zero defects, so the senior person’s job is to find what’s still not right, and yours is to fix it and bring it back — again and again until there are no more marks. A clean first pass is rare and almost suspect. None of this is personal: because the work belongs to the group, revising it isn’t an insult to you. The trap is reading the red ink as criticism and getting defensive, or presenting work as final too early. Build in time for several rounds, expect the polish to be exacting, and treat “still not quite right” as ordinary rather than alarming.
How you did it counts as much as what you produced
A correct result isn’t automatically good work — the way you got there is judged too. Did you follow the proper steps, keep the right people informed, and work in an orderly, transparent way? A strong outcome reached through an opaque or improvised process can still land badly, while a sound process earns trust even when the result still needs work. In practice this means narrating your work as you go: frequent status updates, early consultation, a visible method. The instinct to disappear, solve it your own way, and reappear with the answer tends to make colleagues uneasy, even when your answer is right. Slow down and show your working. Being seen to do things properly — in sequence, with the right people looped in — is itself a large part of what quality means.
The standard lives in people and examples, not in a written spec
Much of what counts as “good enough” isn’t written down — it lives in precedent, in past examples, and in the heads of the seniors who embody the house standard. You’re expected to learn it by watching closely, copying the established form, and repeating it until it’s right, rather than by being handed a checklist. Don’t wait to be explicitly taught; observe how things are done, study previous work, and absorb the unwritten template. Asking for everything to be spelled out can read as not paying attention. The flip side: once you know the established way, follow it — improvising a personal method, even a sensible one, can register as not yet understanding the standard. The fastest way in is to find the model example and match it closely before you try anything of your own.
“Finished” includes the parts nobody will see
Thoroughness reaches past the functional minimum to the parts the recipient may never notice — the formatting, the packaging, the edges, the things that get thrown away after delivery. Work that does its core job but is rough around the periphery reads as unfinished, even careless. Expect attention to neatness and presentation that can feel excessive if you’re used to “good enough to work.” The practical implication is to budget effort for finish, not just function. A document’s layout, a tidy handover, the clean presentation of a file only colleagues will ever open — these all register. Cutting corners on the invisible parts to save time is exactly the kind of thing that quietly lowers how your work is judged. When you think you’re done, the expectation is that you’ve gone to every corner, including the ones nobody asked about.
Good work answers the question they didn’t ask
A large part of quality is reading what’s actually needed — including what was never spelled out — and delivering that, not just the literal request. People are expected to anticipate: to notice the unstated need, to cover the contingency no one mentioned, to bring the thing before it’s asked for. There is a dense everyday vocabulary for this kind of attentiveness, and being good at it is treated as part of basic competence, not merely as being considerate. The practical risk is doing exactly and only what was specified, then being puzzled that it landed flat. Before you deliver, ask what the requester is really trying to achieve and what they’ll need next. Reading the situation and quietly handling the unspoken part is treated as ordinary good work, not as going above and beyond.
When something goes wrong, fix the system and prove it won’t recur
How you handle a mistake matters enormously, and the expected response is specific. Apologize sincerely without making excuses, work out the real root cause rather than waving it off as “human error” or bad luck, and — most important — show concretely what you’ll change so it can’t happen again. Simply saying sorry, or simply patching the immediate problem, isn’t enough; letting the same problem recur is treated as worse than the original mistake. Often a manager will publicly absorb the blame while the team works the fix, so this is a shared, face-saving repair rather than a hunt for someone to punish. The trap is getting defensive, minimizing, or pointing elsewhere — that reads as not taking responsibility. Lead with honest reflection and a credible prevention plan, and a mistake can actually rebuild trust instead of destroying it.
The safe, proven way beats the clever, untested one
Work is often judged good to the extent that it’s unlikely to fail. The robust, proven, well-prepared option is valued over the novel or clever one that carries unknown risk — caution reads as competence, not timidity. Expect a strong preference for tried-and-tested approaches, a demonstrated track record, ample preparation, and margin against things going wrong. The folk image is tapping a stone bridge to test it before crossing, even when it already looks solid. So if you’re proposing something new, lower the perceived risk first: bring evidence, precedent, a small initial step, and answers to the “what if it goes wrong” questions before they’re raised. Pushing an untested idea on confidence alone tends to stall, because the people around you feel the risk you’re asking them to share. De-risk first, and good judgment will be assumed.