Owning Your Work

Definition of Done (DoD)

Before you call a task “done,” check:

  • The output actually exists (doc / demo / merged code / report)
  • Someone else could reproduce or use it from your notes
  • Limitations and assumptions are written down
  • Risks captured (privacy, security, ethics — where relevant)
  • You’ve suggested what to do next

The “owner” mindset

You don’t need to be the boss to act like an owner. You can own:

  • the plan — what happens next and why
  • the evidence — the data or artifact that proves it works
  • the documentation — so the next person doesn’t start from zero
  • the follow-through — closing the loop, not letting things drift

This is the single biggest thing that separates “intern who got hired” from “intern who didn’t.”



Back to top

Professional Skills Guide — GitHub. Suggestions welcome via issues or PRs.

This site uses Just the Docs, a documentation theme for Jekyll.