|
Hey Reader, I’ve been quiet for two weeks. Work got heavy and the newsletter slipped. That’s on me, not you. If you went quiet too, you haven’t failed the challenge. Pick up from wherever your build is right now. We’re in week 10 and the finish line hasn’t moved, so there’s still time to ship. This week’s task is the one most people avoid: share your build publicly for the first time. Not finished. Not polished. Just visible. A few weeks ago you showed it to one person you trusted. This time it goes somewhere a stranger could see it, whether that’s the community, LinkedIn, or wherever you’d normally post. Most people stall here for the same reason. A private build can’t be judged, and a public one can. But waiting costs more than it feels like. A project nobody has seen is a project nobody holds you to. A simple structure for your post:
That last line matters. “What do you think?” gets politeness. “Does the second step make sense?” gets an answer. If you’re behind and your build is smaller than you hoped, share it anyway. A small, honest, visible thing counts. A nearly finished one that nobody has seen doesn’t. What “done” looks like for week 10: Your build has been posted somewhere public, with one specific question attached. The community has been quiet, partly because I’ve been quiet. Post there first, even if it’s just a screenshot. Someone has to go first, and this week it can be you. Next week is about using what comes back to make it better. With three weeks left, there’s no time to waste, and also no need to panic. See you then. |
Each week, I share grounded insights shaped by 15+ years in project management, tech, and creative delivery. Helping you think more clearly about your work, spot opportunities or problems earlier and respond with confidence.