[{"data":1,"prerenderedAt":154},["ShallowReactive",2],{"journal-\u002Fjournal\u002Fbullet-points-vs-numbered-points":3},{"id":4,"title":5,"body":6,"date":140,"description":141,"draft":142,"extension":143,"meta":144,"navigation":145,"path":146,"seo":147,"stem":148,"tags":149,"__hash__":153},"journal\u002Fjournal\u002Fbullet-points-vs-numbered-points.md","Bullet Points vs Numbered Points: Clearer Team Communication",{"type":7,"value":8,"toc":133},"minimark",[9,13,20,25,28,41,44,55,62,66,69,78,81,86,89,93,96,107,110,117,120],[10,11,12],"p",{},"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.",[10,14,15,16],{},"One tiny habit kept slowing those discussions down: ",[17,18,19],"strong",{},"how we write lists when sharing updates or tasks.",[21,22,24],"h2",{"id":23},"the-bullet-point-problem","The bullet-point problem",[10,26,27],{},"You've probably seen this:",[29,30,31,35,38],"ul",{},[32,33,34],"li",{},"Fix the login button",[32,36,37],{},"Fix the configuration data user",[32,39,40],{},"Fix the caching issue on the Redis setup",[10,42,43],{},"Looks fine. Until someone replies:",[45,46,47],"blockquote",{},[10,48,49,50,54],{},"\"Hey, that ",[51,52,53],"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.\"",[10,56,57,58,61],{},"Now you're counting bullets to figure out which item they meant. With 10 items the cost adds up — minutes wasted clarifying ",[51,59,60],{},"before"," fixing anything.",[21,63,65],{"id":64},"the-fix-use-numbers","The fix: use numbers",[10,67,68],{},"Same list, numbered:",[70,71,72,74,76],"ol",{},[32,73,34],{},[32,75,37],{},[32,77,40],{},[10,79,80],{},"Now the reply is:",[45,82,83],{},[10,84,85],{},"\"2. The acceptance criteria seem incomplete.\"\n\"3. I think the issue is on the Redis server, not the setup.\"",[10,87,88],{},"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.",[21,90,92],{"id":91},"small-change-big-impact","Small change, big impact",[10,94,95],{},"Since switching to numbered lists I've noticed:",[70,97,98,101,104],{},[32,99,100],{},"Discussions stay organized",[32,102,103],{},"People reply faster (they know exactly what you're referring to)",[32,105,106],{},"Past messages are easier to reference when debugging or reviewing history",[10,108,109],{},"Not just a tech-team trick. Works for any team — design, marketing, product, ops.",[10,111,112,113,116],{},"Communication isn't only about ",[51,114,115],{},"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.",[118,119],"hr",{},[10,121,122],{},[51,123,124,125,132],{},"Originally published on ",[126,127,131],"a",{"href":128,"rel":129},"https:\u002F\u002Fmenulis.id\u002Fbullet-points-vs-numbered-points-what-i-learned-about-clearer-team-communication\u002F",[130],"nofollow","menulis.id",".",{"title":134,"searchDepth":135,"depth":135,"links":136},"",2,[137,138,139],{"id":23,"depth":135,"text":24},{"id":64,"depth":135,"text":65},{"id":91,"depth":135,"text":92},"2025-10-15","A small writing habit that quietly improves how engineering teams discuss things in Slack — use numbers, not bullets.",false,"md",{"canonical":128},true,"\u002Fjournal\u002Fbullet-points-vs-numbered-points",{"title":5,"description":141},"journal\u002Fbullet-points-vs-numbered-points",[150,151,152],"communication","team","writing","8jo97ovxvfhMSlISSWJxSPejfW_DvLfT1ATMScfO-ig",1787915616861]