[Unpolished] AI is supposed to make us more efficient, right? Yeah... about that. ๐Ÿ˜

By Ali Vahed

๐—ง๐—ฎ๐˜€๐—ธ: Write a requirement document.

๐—•๐—ฒ๐—ณ๐—ผ๐—ฟ๐—ฒ ๐—”๐—œ:
 1. Write the draft.
 2. Spell-check in Microsoft Word, fix errors one by one.
 3. If it is a client facing document, get a friend or colleague to review as a second pair of eyes.
 4. Publish.
๐˜–๐˜ถ๐˜ต๐˜ฑ๐˜ถ๐˜ต: ๐˜ˆ 500-๐˜ธ๐˜ฐ๐˜ณ๐˜ฅ, ๐˜ค๐˜ญ๐˜ฆ๐˜ข๐˜ฏ, ๐˜ฆ๐˜ณ๐˜ณ๐˜ฐ๐˜ณ-๐˜ง๐˜ณ๐˜ฆ๐˜ฆ ๐˜ฅ๐˜ฐ๐˜ค๐˜ถ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต. ๐˜›๐˜ช๐˜ฎ๐˜ฆ ๐˜š๐˜ฑ๐˜ฆ๐˜ฏ๐˜ต: 2 ๐˜ฉ๐˜ฐ๐˜ถ๐˜ณ๐˜ด.

๐—”๐—ณ๐˜๐—ฒ๐—ฟ ๐—”๐—œ
*๐—˜๐˜…๐—ฝ๐—ฒ๐—ฐ๐˜๐—ฎ๐˜๐—ถ๐—ผ๐—ป (๐—š๐—ฒ๐—ป๐—ฒ๐—ฟ๐—ฎ๐˜๐—ถ๐˜ƒ๐—ฒ ๐—”๐—œ):
 1. Write the draft.
 2. Get one of the models to review and update.
 3. Publish.
๐˜Œ๐˜น๐˜ฑ๐˜ฆ๐˜ค๐˜ต๐˜ฆ๐˜ฅ ๐˜–๐˜ถ๐˜ต๐˜ฑ๐˜ถ๐˜ต: 400-๐˜ธ๐˜ฐ๐˜ณ๐˜ฅ ๐˜ฑ๐˜ฐ๐˜ญ๐˜ช๐˜ด๐˜ฉ๐˜ฆ๐˜ฅ ๐˜จ๐˜ฆ๐˜ฎ. ๐˜›๐˜ช๐˜ฎ๐˜ฆ ๐˜š๐˜ฑ๐˜ฆ๐˜ฏ๐˜ต: 1 ๐˜ฉ๐˜ฐ๐˜ถ๐˜ณ.

*๐—˜๐˜…๐—ฝ๐—ฒ๐—ฐ๐˜๐—ฎ๐˜๐—ถ๐—ผ๐—ป (๐—”๐—ด๐—ฒ๐—ป๐˜๐—ถ๐—ฐ ๐—”๐—œ):
 1. Casually chat with your AI agent about what you mean in 5 minutes
2. Your agent writes and publishes the document on your behalf.
๐˜Œ๐˜น๐˜ฑ๐˜ฆ๐˜ค๐˜ต๐˜ฆ๐˜ฅ ๐˜–๐˜ถ๐˜ต๐˜ฑ๐˜ถ๐˜ต: 500-๐˜ธ๐˜ฐ๐˜ณ๐˜ฅ ๐˜ด๐˜ฑ๐˜ฐ๐˜ต-๐˜ฐ๐˜ฏ ๐˜ฅ๐˜ฐ๐˜ค๐˜ถ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต. ๐˜›๐˜ช๐˜ฎ๐˜ฆ ๐˜š๐˜ฑ๐˜ฆ๐˜ฏ๐˜ต: 6 ๐˜ฎ๐˜ช๐˜ฏ๐˜ถ๐˜ต๐˜ฆ๐˜ด.

*๐—”๐—œ ๐—ฅ๐—ฒ๐—ฎ๐—น๐—ถ๐˜๐˜†:
 1. Write the draft.
 2. Feed it to ๐—–๐—ต๐—ฎ๐˜๐—š๐—ฃ๐—ง to review, capture and fix any issues. Repeat this step a few times as it may butcher your note or miss things.
 3. Switch to ๐—š๐—ฟ๐—ผ๐—ธ to criticise your work from customer POV as by now you don’t recognise if it was yours, apply feedback, repeat 3x times as it may miss something. Go back to step 2 for proofreading.
 4. Use ๐—ฃ๐—ฒ๐—ฟ๐—ฝ๐—น๐—ฒ๐˜…๐—ถ๐˜๐˜† to do the citation as there are some new references in this document you are not sure if they are correct, capture and update if anything. Repeat 2x times, go back to step 2 for fresh review.
 5. Get ๐—–๐—น๐—ฎ๐˜‚๐—ฑ๐—ฒ to review and consolidate the article as by now it is over 2000 words long.
 6. If it is client facing document, ask ๐—š๐—ฒ๐—บ๐—ถ๐—ป๐—ถ to do the deep research and review the tone of the document with your previous ones, go back to step 2 for the final review
 7. As by this point, it includes words you’ve never used in your life, get ๐—š๐—ฟ๐—ฎ๐—บ๐—บ๐—ฎ๐—ฟ๐—น๐˜† or other humanizers to review and update, or search for those words in ๐—š๐—ผ๐—ผ๐—ด๐—น๐—ฒ, replace them with words humans actually use.
 8.Exhusted by now? Just publish it anyway.
๐˜–๐˜ถ๐˜ต๐˜ฑ๐˜ถ๐˜ต: 1500-๐˜ธ๐˜ฐ๐˜ณ๐˜ฅ ๐˜ฅ๐˜ฐ๐˜ค๐˜ถ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต, ๐˜ฃ๐˜ฆ๐˜ข๐˜ถ๐˜ต๐˜ช๐˜ง๐˜ถ๐˜ญ๐˜ญ๐˜บ ๐˜ค๐˜ณ๐˜ข๐˜ง๐˜ต๐˜ฆ๐˜ฅ ๐˜ฃ๐˜ถ๐˜ต ๐˜ฏ๐˜ฐ ๐˜ฐ๐˜ฏ๐˜ฆ ๐˜ฉ๐˜ข๐˜ด ๐˜ต๐˜ช๐˜ฎ๐˜ฆ ๐˜ต๐˜ฐ ๐˜ณ๐˜ฆ๐˜ข๐˜ฅ it! ๐˜›๐˜ช๐˜ฎ๐˜ฆ ๐˜ด๐˜ฑ๐˜ฆ๐˜ฏ๐˜ต: 3 ๐˜ฅ๐˜ข๐˜บ๐˜ด

๐—ฅ๐—ฒ๐—ฎ๐—น ๐—ผ๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ: ๐—ข๐—ฝ๐—ฒ๐—ป ๐˜๐—ต๐—ฒ ๐—ฑ๐—ผ๐—ฐ๐˜‚๐—บ๐—ฒ๐—ป๐˜ ๐—ณ๐—ฒ๐˜„ ๐—ฑ๐—ฎ๐˜†๐˜€ ๐—น๐—ฎ๐˜๐—ฒ๐—ฟ, ๐˜€๐—ฒ๐—ฒ ๐—ฎ ๐˜๐˜†๐—ฝ๐—ผ ๐—ถ๐—ป ๐˜๐—ต๐—ฒ ๐˜ƒ๐—ฒ๐—ฟ๐˜† ๐—ณ๐—ถ๐—ฟ๐˜€๐˜ ๐—ฝ๐—ฎ๐—ฟ๐—ฎ๐—ด๐—ฟ๐—ฎ๐—ฝ๐—ต!๐Ÿคฆ


Comments

  1. Ali VahedOctober 7, 2025 at 12:33 PM

    Initially published as a LinkedIn post here : https://www.linkedin.com/feed/update/urn:li:activity:7379012953683120128/

    ReplyDelete

Post a Comment

Popular posts from this blog

Sell Me This Pen!

By Ali Vahed
Image
The Scene:   INT. OFFICE – DAY A sleek high-rise office with floor-to-ceiling windows. A formal interview is underway for a role in a Software development team. A table sits between the INTERVIEWER and the CANDIDATE CASTING The INTERVIEWER: Professional, relaxed. Someone who interviews for any role, from a Sales rep to Software Engineer to C-level Executive, inspired by The Wolf of Wall Street , loves asking questions that throw candidates off guard. The CANDIDATE:   Suited up, a bit nervous but composed. A seasoned software professional: Product or Project Manager, Business Analyst, or experienced Software Engineer, ready for whatever the interview throws their way.    ACTION INTERVIEWER:  (smiling confidently) Please sell me this pen! CANDIDATE  (pauses, raises an eyebrow, thinking: “Seriously? For this role?” but decides to roll with it) Sure... that’s a good question. (leans forward slightly, zoomed in on the candidate's face, thinking out loud) B...
Read more

The PM’s Copilot: Reclaiming Time with AI

By Ali Vahed
Image
Like many PMs, I didn’t really trust AI for serious product work. I mostly used it for general purposes: polishing emails and notes, drafting messages and creating images from time to time. I used AI in a project only as a second opinion and to validate my discovery work, but that was it. For more on that check my earlier  blog post . While AI felt adequate for technical tasks or copywriting, it didn’t feel reliable for the messy, ambiguous world of product management where curiosity, judgement, and breaking patterns matter most. Then everything shifted. Here is my experience report.
Read more

Product Helmsmanship (P1): Balancing Strategy, Execution, and the Storms in Between

By Ali Vahed
Image
Product Management often feels like steering a ship through unpredictable seas. Over my career, I’ve learned when to grip the wheel and dive into execution, when to step back and chart the strategic course, when to find that sweet spot in between, and when to simply hand the helm to the crew and trust them to steer. I call this balance Product Helmsmanship . The Origin Story When I first stepped into tech, I started from the lower decks. I began in execution, first as a developer writing code since I was 12, then as a Business Analyst turning requirements into documents and diagrams right after university, and later as a Project Manager focused on delivery. The transition into Product Management felt natural , but in the early years my role often felt like translation, helping business leaders and technical teams understand one another, sometimes mapping business requirements to technical jargon and vice versa. Over time, I realised Product Management is less about translating and ...
Read more