Setting Up Project Management Workflows

Instead of asking "what should I automate?" Focus on WHY you should automate and HOW it solves the data problem. Most data engineers automate the wrong things at the wrong time. Here's the framework I use after 8 years of building production systems: ✅ AUTOMATE WHEN: → Task runs daily/weekly → Human errors cause outages → Work blocks other priorities → Team growth = more manual work Examples: Reports, schema checks, alerts ❌ DON'T AUTOMATE WHEN: → Task happens quarterly → Requirements change weekly → Process isn't understood yet → Manual steps reveal insights My rule: If it’s done 3+ times, script it; 10+ times, automate it; fails 5+ times, redesign it. Automate what matters, when it matters—not everything! Here's how Airflow makes data automation ridiculously easy: 🎯 The Magic Triangle: → Scheduler: Triggers workflows on time → Executor: Distributes work to available workers → Workers: Actually run your Python code 💾 Smart State Management: → Metadata DB: Tracks every task run → Queue: Manages task priorities → Web UI: Visual monitoring & debugging 🔄 Why It Works: → Write Python DAGs once → Airflow handles the rest → Automatic retries & error handling → Parallel task execution → Visual dependency tracking Real Example: Instead of: ❌ Cron jobs that fail silently ❌ Manual dependency management ❌ No visibility into failures You get: ✅ Visual workflow monitoring ✅ Automatic failure notifications ✅ Smart task scheduling ✅ Easy debugging & restarting Image Credits: lakeFS The Bottom Line: Apache Airflow turns complex data workflows into manageable Python scripts. What's your biggest pipeline automation challenge? #data #engineering

Most project managers think Claude Cowork is a tool for developers. It is not. It is your AI teammate for project management. No code. No technical background required. Just a smarter way to manage projects, stakeholders, and delivery. AI Fluency is fast becoming part of job requirement and expectation. Here is how to get started and what it can do for you every week. → 1. Set up your CLAUDE.md file first Tell your teammate who you are, your role, your projects, and how you communicate. It takes 5 minutes. From that point, it stops being generic and starts working the way you work. → 2. Use Plan Mode before any complex task Press Shift and Tab before you give it a brief. Your teammate proposes a plan and waits for your approval before doing anything. You stay in control. Nothing happens without your sign-off. → 3. Let it remember Your teammate saves what it learns about your projects automatically. You do not need to re-explain context every time you open a new session. The longer you use it, the better it knows your work. → 4. Connect your tools once Gmail, Slack, Notion and Jira link to your account once. Your teammate uses them in every session without any setup. Zero configuration. They just follow you. → 5. Set how hard it thinks For simple tasks like status updates, keep it light. For complex tasks like risk planning, ask it to think deeper. Match the effort to the task and it becomes significantly more useful. Here is how you can use it every week. Status reports and executive updates. Give Claude your project data and it drafts the narrative. You refine and send. What used to take an hour takes ten minutes. Risk identification. Describe your project and ask for a pre-mortem. It surfaces blind spots before they become escalations. Meeting preparation. Ask it to brief you before every key session. Agenda, history, open actions. You walk in prepared every time. Lessons learned. Paste your retrospective notes and ask for themes. A whole workshop distilled into a structured output in minutes. None of this is theoretical. This is Tuesday afternoon project management. Where to start this week. Monday — Download the Claude desktop app and set up your CLAUDE.md. 10 minutes. Wednesday — Use Plan Mode on your next complex task. See how it proposes before it acts. Friday — Ask it to draft your weekly status report from your project notes. See what comes back. If you want to go deeper than this and build real AI capability across your full project lifecycle, the AI Capability Cohort for Project Managers starts on 4th May. Small group. Hands on. Built around doing and not watching. DM me APM and I will share more details with you.

3 Workflows I've Automated for in-house teams. ① Ask Legal ② Procurement ③ Contract Review (not just the review!) 1. Ask Legal [or any department for that matter 🤷🏼♀️] You've heard me talk about legal teams and knowledge management. Long story short, your legal team is answering the same 20 questions over and over 😵💫 A simple way to save a CHUNK of time answering questions from the business (enabling them to go faster) ALL while having complete control & keeping a human in the loop? ↪️ Set up an 'Ask Legal' bot in your comms platform. ↪️ Sync it with your knowledge base (e.g GDrive/Notion/Sharepoint). ↪️ Set up your custom instructions (Want it to tag Bob on privacy questions only, specifically on a Tuesday? No problem).  ↪️ Don't want the answer to go straight out to the business without reviewing it first? Cool, turn on co-pilot mode. The result? 60-80% fewer repetitive queries. Your team focuses on the high value things that need a human lawyer. 2. Procurement Businesses have 100's of tools, but when departments don't speak to each other you end up with duplicate tools & subscriptions 😭 💵 🚽.  What if there was a way for the business to find out in <1 minute if there was a tool available that covered their needs, before needing to spend some hard secured department budget? Moreover, what if I told you, they could kick off the internal procurement process from the comfort of your comms platform? Team member : “Do we already have a tool for X?” in Slack/Teams ✅ Bot checks knowledge base (policies, procurement tool). ✅ If a match is found, it shares the approved tool & owner to contact. ✅ If not, the bot can ask the user for more info and direct them with next steps to kick off the procurement process from inside Slack/Teams. Ensuring your users ACTUALLY follow the process, without adding friction. Did I just see your CFO cry tears of joy? 3. Third Party Vendor Contract Review & Project Management Getting AI to redline a contract (as a first pass) is a huge win, but there's still the other pieces of the process missing, like: 🤷🏼♀️ The business figuring out IF legal review is even needed (according to company policy). 📨 The business actually submitting the contract to legal. 😩 Managing review capacity within the legal team. 🖥️ Getting the legal team to log & update the PM tool. The list never ends. Legal reviews only what actually needs their eyes, turnaround times improve, and the business stops pinging the team for “update pls?” in Slack : ) TLDR; Most legal teams are drowning in admin work that could be automated. I've built all of these using simple processes and tools (that I've found most businesses have). You also know I love a good Figma flow. So I’ve built them for all three of the above (see a sneak peak below). Want the entire thing? Comment "FLOWS" and I'll send them over. Also, tell me what you want to see - more of the above or step-by-step how-to build videos?

𝗜 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗠𝘆 𝗣𝗠 𝗪𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝗶𝗻 10 𝗠𝗶𝗻𝘂𝘁𝗲𝘀—𝗛𝗲𝗿𝗲’𝘀 𝗘𝘅𝗮𝗰𝘁𝗹𝘆 𝗛𝗼𝘄 👇 Product teams waste 17% of their time on documentation and comms (McKinsey). And I automated the most tedious part for me using Lovable - with zero code.  👉 Turning detailed PRDs into internal launch comms, Notion posts, stakeholder briefs, and checklists. It was eating up hours every week — across product and growth team. So I thought, what if we just automated it? 🤔 𝗜 𝗯𝘂𝗶𝗹𝘁 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁 𝘁𝗵𝗮𝘁: ✅ Reads our PRDs ✅ Extracts the key details ✅ Generates a Notion-ready launch post ✅ And even creates a structured PM checklist No code. Just a few smart prompt blocks. Now this agent saves our team 4–6 hours per launch, and keeps everyone aligned without the usual back-and-forth. In this post, I’m breaking down exactly how I built it step by step: - My exact 10-step framework   - Battle-tested prompts you can copy   - Common pitfalls (and how to avoid them)  👉 Swipe through to see how you can build your own AI teammate too. P.S. Should product teams have an "AI Agent Manager" role by 2025?

The most desired AI PM qualification in 2025 is shipping production-ready B2B agents. Here’s my 3-step playbook to go from idea to production: Step 1: Build a Scrappy Prototype - Forget complex front-ends. Start with no-code tools (n8n/ MSFT Co-pilot Studio) and focus on speed. - Describe your goal in English: Use tools like Microsoft Copilot Studio to build an agent by simply describing what you want it to do. - Use existing apps: Integrate with Mail or Slack for your front-end. Meet your users where they already are. Start with a one-pager: Your goal is a working prototype based on a simple requirements doc, not a 50-page PRD. Step 2: Evaluate Ruthlessly - Building is easy. Building a reliable agent is hard. This is where most people fail. - Acknowledge the limits: The tech for full human replacement isn't there yet. Reasoning is still hacked into models, and accuracy on hard benchmarks is low. The cost of stabilizing a reliable agent can be 10-100x the cost of the initial build. - Use the HHH Framework: Evaluate your agent on three simple questions: Is it Helpful? Is it Honest? Is it Harmless? Set Clear Launch Criteria: Work with experts to define what "good" looks like and set objective scores (e.g., "70% helpfulness") before you ship to a wider audience. Step 3: Iterate Relentlessly - Use your evaluation data to guide your roadmap. - Focus on Assisting, Not Replacing: The winning strategy is building tools that assist people and deliver tangible artifacts. Think of a tool like Loveable(now with cloud+AI support) that builds a functional website, not just code snippets. - Let the Data Guide You: Use the feedback and evaluation scores from your early users to set your next targets and features. This data loop is what turns a prototype into a scalable product. Very few AI PMs have actually done this, and you’ll immediately stand out if you do. I’ve seen it myself: This is the exact process that members of my cohort on @Maven have used to automate complex workflows and save their companies millions.

The gap between a project estimate and kick-off can be a killer. (Automation Tip Tuesday 👇) For service-based businesses (any business, really!), friction is the ultimate profit killer. A client agrees to the scope, but then… paperwork, approvals, deposits — it all creates delay and destroys momentum. One of our recent automation projects tackled this head-on. Our client, a high-end home remodeling firm, was using a host of tools to manage their workflows, but the process of moving from an estimate to a signed agreement (with a deposit) was still manual and disjointed. We streamlined it. Now: ✅ Estimates auto-generate in Airtable, pulling project details from a structured pricing database. ✅ Signed agreements trigger deposits automatically — Dubsado sends the contract, collects e-signatures, and instantly generates an invoice in QBO. ✅ Once the deposit is paid, the project kicks off in Google Calendar and updates the team’s task board. The result? Faster approvals, fewer dropped leads, and a smoother experience for homeowners eager to begin their renovations. Software should work for you, not slow you down. If your business has gaps in its process, automation might be the missing piece. What’s killing your momentum? -- Hi, I’m Nathan Weill, a business process automation expert. ⚡️ These tips I share every Tuesday are drawn from real-world projects we've worked on with our clients at Flow Digital. We help businesses unlock the power of automation with customized solutions so they can run better, faster and smarter — and we can help you too! #automationtiptuesday #automation #workflow #efficiency

𝗛𝗼𝘄 𝗜 𝗴𝗲𝘁 𝗼𝘂𝘁 𝗼𝗳 𝗵𝘂𝘀𝗹𝘁𝗲 𝗮𝗻𝗱 𝘀𝘁𝗿𝘂𝗴g𝗹𝗲 𝗶𝗻 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘂𝘀𝗶𝗻𝗴 𝗔𝗜 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 I’ve always worked on large corporate and consulting projects throughout my entire career. I can really say that I know the pain points in project workflows and collaboration. Project work is full of hidden friction: 🔄 Repetitive updates 🧩 Misaligned communication 📄 Documentation that never gets finished 🤯 Mental overload from managing everything Project work shouldn’t be this hard. I discovered that AI can be a game-changer. It’s a toolbox that quietly removes the friction, so teams can actually focus on creating value. 👉 Here are 3 AI workflows I can’t imagine project work without: 📊 Project Status Report Drafting 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: Creating regular updates is repetitive and often delayed. 𝗔𝗜 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: AI drafts weekly or monthly status reports from task data and notes. 𝗜𝗺𝗽𝗮𝗰𝘁 / 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀: Ensures consistent updates and professional formatting. 📍 Process Documentation Writer 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: Documenting project workflows takes too long. 𝗔𝗜 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Converts bullet points into formal standard operating procedures. Rewrites complex content into plain simple language that everyone understands. 𝗜𝗺𝗽𝗮𝗰𝘁 / 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀: Supports scaling and standardisation. 👥 Meeting Summary and Clarification Generator 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: Not everyone captures the same notes during meetings. Missing information or perspectives can lead to delays or conflicts. Hidden conflicts influence team collaboration in a bad way. 𝗔𝗜 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: AI creates a neutral, complete summary including action items and decisions. Lists missing information, reveals hidden conflicts. 𝗜𝗺𝗽𝗮𝗰𝘁 / 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀: Ensures team alignment and saves time consolidating notes. Helps move forward faster and improves team collaboration by avoiding or solving conflicts. AI can really be a supporter for project teams, not replace them. And it is a true game-changer. I’m really happy to announce that Christoph Schmiedinger and I will start a content series about the practical usage of AI in project management and product management. We will keep you posted. Leave a comment about your experiences. Let’s learn together.

Interview Conversation Role: RTE Topic: Leveraging Jira Align 👨💼 Interviewer: "As an RTE, how do you use Jira Align to manage dependencies across teams in an Agile Release Train?" 🧑 Candidate: "Jira Align helps track tasks and dependencies between teams." 👨💼 Interviewer: "Imagine Team A is blocked because Team B’s feature isn’t ready, and this delay could impact the PI objectives. How would you use Jira Align to resolve and track such dependencies?" 🧑 Candidate: "I’d ask the teams to resolve it in their sync-up meetings." What a skilled RTE should have answered: ---------------------------------------------- 💡 Jira Align is a powerful tool for visualizing and proactively managing dependencies across teams and ARTs. Here’s how I’d approach the situation: ✍ 1. Proactive Identification: During PI Planning, I’d ensure teams clearly log dependencies in Jira Align’s Dependency Map. This allows us to identify blockers early and assess their impact on delivery timelines. ✍ 2. Continuous Tracking: I’d regularly review the Program Board in Jira Align to monitor the progress of dependencies. For example, if Team A relies on Team B’s feature, Jira Align enables both teams to align their schedules and track progress through automated updates. ✍ 3. Issue Resolution: In case of a delay, I’d leverage Jira Align to trigger an escalation. The tool’s centralized data makes it easy to identify priority dependencies, communicate risks to stakeholders, and propose adjustments to mitigate the impact on PI objectives. ✍ Example in Action: In a previous ART, a critical dependency delay between two teams risked derailing a feature release. By using Jira Align’s Portfolio Room, we aligned stakeholders, reprioritized deliverables, and reallocated capacity to keep the train on track. ✍ Impact: Jira Align ensures transparency, alignment, and faster conflict resolution, ultimately enabling ARTs to deliver value predictably. ✨ Key Takeaway: Managing dependencies is about more than meetings—it's about leveraging tools like Jira Align to proactively track, manage, and resolve risks. Transparency is the backbone of seamless execution. Join community for deeper insights: Link in the comment below #SAFe #ReleaseTrainEngineer #JiraAlign #AgileTransformation #DependencyManagement

I hate it when people mix up Product, Project, Program management. My blood boils when those people are founders or product leaders. So once and for all, let us settle this. Let's understand what the 3 roles truly mean. 𝗧𝗟𝗗𝗥: 1️⃣ 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿𝘀: own WHY and WHAT for a product 2️⃣ 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀: own WHEN for a 𝘴𝘪𝘯𝘨𝘭𝘦 project 3️⃣ 𝗣𝗿𝗼𝗴𝗿𝗮𝗺 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀: own WHEN for a 𝘱𝘰𝘳𝘵𝘧𝘰𝘭𝘪𝘰 of connected projects 1️⃣ 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀 (𝗣𝗠𝘀): 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗮𝗿𝗲𝗮: Primarily focus on the 𝘷𝘪𝘴𝘪𝘰𝘯, 𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺, and 𝘳𝘰𝘢𝘥𝘮𝘢𝘱 of an entire (or a part of the) product. They also define success criteria and set goals for their product. 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝘁𝗮𝘀𝗸𝘀: • talk to users, research market, talk to experts • they do the above to identify problems to solve • prioritise the problems based on impact • decide which problems to solve in which order • work with others to create multiple solutions • prioritise the solutions based on impact • decide which solution to create in which order • collaborate with eng. and design on solution design • influence multiple other teams to believe in and support their ideas and plans 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗰𝗿𝗶𝘁𝗲𝗿𝗶𝗮: PMs are successful when they create impact for the business and users. Common metrics to measure impact - revenue, no. of users, profit, retention, etc. 2️⃣ 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀 (𝗣𝗷𝗠𝘀): 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗮𝗿𝗲𝗮: Primarily focus on creating the project plan. A project plan (aka delivery plan) details WHO does WHAT and WHEN. PjMs also ensure all task owners are on track, there are not delays and issues. 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝘁𝗮𝘀𝗸𝘀 • work with PMs and eng to identify interdependencies • create realistic task deliverables and timelines • keep everyone on track • measure progress • highlight and escalate if teams are off track • identify risks, create mitigation plans • act as central point of progress, issues, deadlines for all teams involved    𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗰𝗿𝗶𝘁𝗲𝗿𝗶𝗮: on time delivery of projects without any issues 3️⃣ 𝗣𝗿𝗼𝗴𝗿𝗮𝗺 𝗠𝗮𝗻𝗮𝗴𝗲𝗿𝘀 (𝗣𝗴𝗠𝘀) 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗮𝗿𝗲𝗮: similar to project managers but for a portfolio of interconnected projects. PgMs also primarily own the delivery of projects, but they ensure that projects are meeting larger team/org goals. 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝘁𝗮𝘀𝗸𝘀: same as PjMs but for multiple projects 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗰𝗿𝗶𝘁𝗲𝗿𝗶𝗮: same as PjMs but across multiple projects. With the added pressure of meeting relevant business goals. -- 𝗖𝗮𝘃𝗲𝗮𝘁 𝟭: Different org defines these roles differently. 𝗖𝗮𝘃𝗲𝗮𝘁 𝟮: There are a lot of grey, overlapping areas in the 3 roles -- How does your org define these roles? Let me know in comments!

One matrix to rule your project Imagine this: You are on a cross-functional project team, a group of talented and skilled individuals. You begin working with the team on project activities that align with your skill sets. When some progress is made, others suddenly start questioning or commenting on your role in the project. What value are you adding? Why are you even required on the project? You are not doing what you are expected to do You expect others to do certain things, whereas others expect you to do those things.   Sound familiar? I have been there. We have all been there. It is that moment when you realize that the roles of the team members are not clear. There is so much confusion, and it is not clear who is responsible for what. That is exactly where the RASIC matrix comes in. It's not just another project management tool; it's the engine, the compass, and the clear sailing instructions a project team desperately needs.   Now, picture this instead: You are kicking off a new project. Before the first task even begins, you and your team collaboratively map out every key activity. For each activity, you ask: - Who is Responsible (R) for different activities involved in the project? - Who is Accountable (A) – the single person who signs off, owns the outcome of different actions and takes the ultimate bow (or takes the hit)? - Who needs to be Supportive (S), offering resources or assistance? - Who needs to be Consulted (C) for their invaluable input before a decision is made? - Who needs to be Informed (I) about the progress or decision after it's happened? ....and just like that, the ambiguity goes away. Suddenly, everyone knows their role. There are no more assumptions, no more duplicated efforts, and definitely no more "I thought you were doing that!" or "You are not doing your work properly!" moments. The person Responsible gets to work, knowing they have the backing of the Accountable person. The Consulted feel valued, and the Informed stay in the loop without constantly asking about the progress. The result? The team moves swiftly and directly towards the finish line. Collaboration flourishes because clarity exists. This is the tool that I always emphasize using in the training sessions that I conduct. Takeaway: If your projects ever feel like that spinning boat, give RASIC a try. It’s a simple yet powerful matrix that can transform confusion into clarity, and effort into impact.   What are your experiences with RASIC? Share your success stories or challenges in the comments below. #ProjectManagement #RASIC #RACI #Teamwork #Leadership #Communication Picture credits: https://lnkd.in/dk5kpEtT