[{"data":1,"prerenderedAt":184},["ShallowReactive",2],{"journal-list":3},[4,41],{"id":5,"title":6,"body":7,"date":27,"description":28,"draft":29,"extension":30,"meta":31,"navigation":32,"path":33,"seo":34,"stem":35,"tags":36,"__hash__":40},"journal\u002Fjournal\u002Fmaking-of-a-manager.md","The Making of a Manager — Julie Zhuo",{"type":8,"value":9,"toc":23},"minimark",[10,14,20],[11,12,13],"p",{},"One-liner I keep re-reading:",[15,16,17],"blockquote",{},[11,18,19],{},"You don't have to do everything yourself, be the best at everything yourself, or even know how to do everything yourself. Your job, as a manager, is to get better outcomes from a group of people working together.",[11,21,22],{},"That's it. That's the whole job description.",{"title":24,"searchDepth":25,"depth":25,"links":26},"",2,[],"2026-05-14","One-liners I keep coming back to from Julie Zhuo's book on what management actually is.",false,"md",{},true,"\u002Fjournal\u002Fmaking-of-a-manager",{"title":6,"description":28},"journal\u002Fmaking-of-a-manager",[37,38,39],"books","management","one-liners","ynp-nBpczot0Zz3a-pspigrRwSb_bj37-AucawUmATA",{"id":42,"title":43,"body":44,"date":173,"description":174,"draft":29,"extension":30,"meta":175,"navigation":32,"path":176,"seo":177,"stem":178,"tags":179,"__hash__":183},"journal\u002Fjournal\u002Fbullet-points-vs-numbered-points.md","Bullet Points vs Numbered Points: Clearer Team Communication",{"type":8,"value":45,"toc":168},[46,49,56,61,64,77,80,90,97,101,104,113,116,121,124,128,131,142,145,152,155],[11,47,48],{},"As a software engineer, I spend hours every week discussing things on Slack — design systems, code reviews, deploy timing. Remote work made messaging the default channel.",[11,50,51,52],{},"One tiny habit kept slowing those discussions down: ",[53,54,55],"strong",{},"how we write lists when sharing updates or tasks.",[57,58,60],"h2",{"id":59},"the-bullet-point-problem","The bullet-point problem",[11,62,63],{},"You've probably seen this:",[65,66,67,71,74],"ul",{},[68,69,70],"li",{},"Fix the login button",[68,72,73],{},"Fix the configuration data user",[68,75,76],{},"Fix the caching issue on the Redis setup",[11,78,79],{},"Looks fine. Until someone replies:",[15,81,82],{},[11,83,84,85,89],{},"\"Hey, that ",[86,87,88],"em",{},"Fix configuration data"," still has a bug.\"\n\"The second point seems to be missing the acceptance criteria.\"\n\"Hmm… number 3 looks like it's not actually a Redis issue.\"",[11,91,92,93,96],{},"Now you're counting bullets to figure out which item they meant. With 10 items the cost adds up — minutes wasted clarifying ",[86,94,95],{},"before"," fixing anything.",[57,98,100],{"id":99},"the-fix-use-numbers","The fix: use numbers",[11,102,103],{},"Same list, numbered:",[105,106,107,109,111],"ol",{},[68,108,70],{},[68,110,73],{},[68,112,76],{},[11,114,115],{},"Now the reply is:",[15,117,118],{},[11,119,120],{},"\"2. The acceptance criteria seem incomplete.\"\n\"3. I think the issue is on the Redis server, not the setup.\"",[11,122,123],{},"Instantly clear. No counting, no guessing. Months later when you scroll back through old threads, you'll thank yourself — numbered discussions are way easier to track.",[57,125,127],{"id":126},"small-change-big-impact","Small change, big impact",[11,129,130],{},"Since switching to numbered lists I've noticed:",[105,132,133,136,139],{},[68,134,135],{},"Discussions stay organized",[68,137,138],{},"People reply faster (they know exactly what you're referring to)",[68,140,141],{},"Past messages are easier to reference when debugging or reviewing history",[11,143,144],{},"Not just a tech-team trick. Works for any team — design, marketing, product, ops.",[11,146,147,148,151],{},"Communication isn't only about ",[86,149,150],{},"what"," you say. It's about how easy it is for others to understand and respond. One of those small lessons I learned the hard way.",[153,154],"hr",{},[11,156,157],{},[86,158,159,160,167],{},"Originally published on ",[161,162,166],"a",{"href":163,"rel":164},"https:\u002F\u002Fmenulis.id\u002Fbullet-points-vs-numbered-points-what-i-learned-about-clearer-team-communication\u002F",[165],"nofollow","menulis.id",".",{"title":24,"searchDepth":25,"depth":25,"links":169},[170,171,172],{"id":59,"depth":25,"text":60},{"id":99,"depth":25,"text":100},{"id":126,"depth":25,"text":127},"2025-10-15","A small writing habit that quietly improves how engineering teams discuss things in Slack — use numbers, not bullets.",{"canonical":163},"\u002Fjournal\u002Fbullet-points-vs-numbered-points",{"title":43,"description":174},"journal\u002Fbullet-points-vs-numbered-points",[180,181,182],"communication","team","writing","8jo97ovxvfhMSlISSWJxSPejfW_DvLfT1ATMScfO-ig",1778772262743]