
Whether it's #DevRel, side projects, or learning a new coding skill, knowing how to properly scope a project can feel like a superpower.


This could be a short blog post, a 30 second screencast, a small command line app, or part of a new app feature. It needs to be easy to know if it's finished or not.

This isn't a hard & fast rule, but the goal is to keep it under a week so you can build momentum.


Factor in time you might need for things like publishing, marketing, deployment, cross-posting, etc.
There's great benefit to thoughtfully running through a whole process.

You want it to push you to learn something new without completely paralyzing you.

You'll get better at the creative side and you'll also get better at building systems around the steps that are time-consuming in the beginning.

Of course not everything can neatly fit into a few days or a week, but the more you can practice slicing off tiny chunks to work through quickly and measure, the better you can adjust course throughout a big project.

If you found this thread helpful, you'll probably like my newsletter. Each week I send out a practical, actionable way to improve as a developer and developer advocate. Sign up here: https://developermicroskills.com