Setting Up Project Management Workflows

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.

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

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

After 5 years helping 800+ companies streamline onboarding, here's the most underestimated way I’ve found to eliminate delays: Prescriptive playbooks. Most onboarding failures happen before customers even start using your product. We dump endless configuration options on them and ask them to figure out what they want. I know a software vendor in our space who gives a spreadsheet with 800 rows for their customers to fill, before they can “start” implementing. The result? Analysis paralysis, delayed launches, and frustrated users wondering if they're doing it "right”. Customers do sometimes blame themselves for these delays, but they’ll steer away from your software and software in your space if they have this experience Ever notice how many tools give you templates instead of a blank page? There's a reason for that. Smart companies use more prescriptive and preset configurations: For ex, Slack: Suggested channels and workflows This leverages two psychological principles: → People are more likely to use tools when they feel they've already started → Once started, momentum keeps them going Instead of asking "What do you want to set up?" start with, "Based on companies like yours, here's what we recommend." Map your customer types to proven configurations. Present these as the starting point. This approach eliminates decision fatigue, ensures customers benefit from your best practices, and de-risks launches with proven setups Your customers don't want infinite choices. They just want confidence that they're set up for success.

👉 Map Dependencies to Find Bottlenecks It is hard for a team to ship fast when it has to wait on other departments, teams, or suppliers to do something they depend on. 💤 For example, when deployments are performed by an external team that is swamped with other work. Or when another department has to perform specialized testing before approval is given. Whatever their dependencies, they are generally outside of the control of a team. 🤷♀️ That makes the delays unpredictable. Even when a team considers something “Done”, weeks or months may pass before their work actually reaches stakeholders. This greatly impedes a team’s ability to work empirically and reduce the risk associated with complex work. This experiment is about creating transparency around dependencies and their effect on your team’s ability to ship fast. It was inspired by the Dependency Spiders in Jimmy Janlén's “96 Visualization Examples” (which contains many other awesome visualizations 🎉 ). To implement this experiment, do the following: 1️⃣ Draw your team in the middle of a big piece of paper. Together, create a list of the teams, people, and departments you frequently need something from to create a Done Increment or release it. Whose approval do you need? 🤔 Who needs to perform an activity for your team to continue? Draw the sources you depend on around your team, like the legs of a spider. 🕷 2️⃣ Whenever your team needs something from someone outside the team, capture the request and the date it was issued on a sticky note and put it next to the source on the canvas. When the request is fulfilled, write the number of days you had to wait on the sticky. At the end of the Sprint, calculate the average wait time in days for all the fulfilled requests and move them to an archive. 3️⃣ Use the Dependency Spider and the average wait time as input for your Sprint Reviews and Sprint Retrospectives. 🤔 What actions can you take to reduce the impact of dependencies on your ability to ship? 🤔 How can you include and collaborate with them to remove or reduce dependencies? 🤔 How can you leverage support from your Product Owner and stakeholders to change your team's environment so that you can ship value to them faster? What are your thoughts after reading this post❓ What other ideas do you have❓

Stop “welcoming” new hires. Give them a win in 30 days instead. When I first hired 8 years back, I thought the best onboarding was all about making new hires feel at home. I was wrong. New hires actually struggle with: → Understanding the business and their role. → Aligning with company culture and expectations. → Getting that first “win” to build momentum. → Building relationships with colleagues. I’ve now completely changed our onboarding process. The only goal is to get new hires to their “first win” fast. Instead of generic training, we work backward from their first big achievement. Here’s the framework: Step 1: Define the “first win” (within 30 days) Every new hire gets a specific, meaningful milestone. 1. It should be important enough that not doing it has a business impact. 2. Something that pushes them but is achievable with team collaboration. 3. It should give them real insight into how we operate. Our new Demand Gen Marketer’s first win was securing Market Development Funds (MDF) from a partner. To do this, they had to: - Work with our internal team. - Engage with a partner manager. - Propose a campaign relevant to both companies. This wasn’t just a task (it was a meaningful contribution). Step 2: Provide context (without overloading them) Most onboarding programs drown new hires in endless presentations. We limit training to what they need for their first win. 1. A 45-minute deep dive on the company’s journey, priorities, and challenges. 2. Targeted learning on only what’s relevant for their milestone. 3. Hands-on guidance instead of passive training. For the Demand Gen hire, we focused on: - Who the partner manager was and their priorities. - How the partnership worked. - What MDF campaigns typically get approved. Step 3: Align them with our work culture Culture isn't learned in a handbook. It’s experienced. Every new hire is paired with a mentor to guide them through: → Quality Standards → What "good" looks like in our company. → Processes & Tools → How we work and collaborate. → Feedback Loops → How we review, iterate, and improve. The result? New hires achieve something meaningful within their first month. They feel pride, momentum, and confidence (not just onboarding fatigue). Great onboarding isn’t about information. It’s about impact. 💡 How do you set up new hires for success?

I’ve spent 300+ hours coaching PMM through onboarding. Here is the most important tip I have: Build your 30/60/90 day plan backwards. 👇 Most PMMs' onboarding plans start with a to-do list: --> Meet with cross-functional teams --> Review past launches --> Read docs The problem with this approach is that you never feel like you’re doing enough, and everything seems equally important. You also have no real sense of how long things will take. It makes it nearly impossible to prioritize your time or align expectations with your manager. When I coach PMMs through onboarding, I tell them to build it BACKWARDS. Start at day 90 and determine, by then: – What do you want to have delivered? – What do you need to have learned? – Who needs to know and trust you? Then work backwards and chunk it down. One of my clients just joined as the first PMM at a 50-person startup. In her second week, she was already getting requests for: -> Improving the ICP and messaging -> Updating the sales enablement decks -> Building a launch strategy 😬 As you can imagine she was pretty stressed and needed a good way to set the right expectations and also plan her work. So we built a new plan, working backwards from day 90, which included: ✅ 3 streams: deliver/learn/meet ✅ Tied each project to an outcome, not just a task ✅ Chunked out each project into smaller milestones ✅ Treated learning as a deliverable, so her ramp time was visible She used that plan to align with her manager, which not only set clear expectations but also showed she could think strategically and take initiative from day one. If you’re onboarding in a startup, remember the key is not to add more, but to work backwards, and then clearly communicate that to set the right expectations. Let me know how I can help. 💪 #productmarketing #newjob #coaching #strategy

I discovered a single workflow that perfected onboarding. The best part? New hires feel like they belong - before they even start. Here's the exact process we built: We automate policies. We checklist productivity. But we forget to build belonging. And that’s where most companies lose their best people before they even start. 🧠 High-performance onboarding isn’t just paperwork and passwords. It’s relationship architecture. It’s trust, built deliberately. It’s clarity that says: “We’ve got you.” Here’s what elite onboarding systems do before day one: ✅ Schedule 1:1 meetings with teammates and stakeholders ✅ Assign a buddy or mentor as a daily go-to ✅ Provide access to past projects so new hires understand legacy context ✅ Deliver a crystal-clear 90-day ramp-up plan (culture → role → execution) Most orgs? They overload day one. Ghost on day three. And wonder why confidence never ramps. The real cost? Disengagement. Attrition. Low-trust teams. And it compounds fast - especially in regulated, fast-scaling environments. Let’s flip the script: ✔️ Prepare everything before day one ✔️ Automate the logistics ✔️ Focus the human effort on connection When onboarding is done right, it doesn’t just boost productivity. It anchors culture. It retains talent. It scales your systems and your people. We’ve built Process Street to help you do exactly that. Without losing the human in the process. 👋 Want to see how we’ve helped teams like Salesforce and Calderys level up onboarding (and compliance) across global teams? Check out the link in the comments! Let’s make day one feel like belonging.

Seamless Onboarding: The Digital Key to Talent Retention Bringing new talent into your organization often feels like a gamble. Almost 20% of new hires leave within 45 days, wasting resources and disrupting teams. This early turnover highlights a critical gap in many organizations. With an "Onboarding Success Dashboard", it streamlines everything else. It automates legal forms, IT setup, and HR documents. This eliminates paperwork for new hires and stakeholders. It ensures all necessary tools are ready on day one. This digital system frees your teams for higher-value work. It saves time and prevents frustration. We must ensure new hires feel connected, productive, and supported from day one, with a "Pre-Boarding Adventure Map" that builds excitement. This personalized digital guide starts at offer acceptance. It clarifies expectations and introduces company culture. It reduces first-day jitters. Additionally, "Reverse Mentoring" pairs new hires with senior leaders. This shares fresh insights and builds early connections. Short "Cross-Functional Immersions" provide a holistic business view. Then, each new hire starts with a "First Project Sprint". This immediate, tangible task allows them to contribute within weeks, not months. It accelerates learning and fosters a sense of purpose. This approach moves new talent to full productivity faster. These human-centric strategies drive real operational excellence. They significantly improve retention. They accelerate productivity and enhance both employee and customer experiences. They also manage costs and risks tied to talent acquisition. This transforms onboarding from a compliance exercise into a strategic growth engine. How do you ensure your new talent thrives? Let Digital Transformation Strategist discuss them with you.

Steal this automated workflow to make sure your onboarding kickoff calls get booked promptly after a deal closes in HubSpot. Getting ghosted once a deal closes is all too common for onboarding teams. By creating a process that communicates what's next AND alerts our teams if things get off track we can make sure we start making progress quickly. Here’s how it works: 1. Trigger this workflow when a new ticket is created in our onboarding pipeline. 2. Rotate the ticket between members of our onboarding team to assign an owner. 3. IF/THEN Check who has been assigned as an owner of the ticket and create a branch for each. 4. For each possible owner branch set the value of “Owner Meeting Slug” to that team member's meeting link slug. 5. Create an Arrows customer facing onboarding plan for this customer (that includes the owners meeting link). 6. Copy the URL to access the newly created plan to a property on the ticket. 7. Send an automated welcome email using the “Welcome” template to associated contacts that includes a link to the onboarding plan. 8. Delay the workflow for 1 day. 9. IF/THEN Check if a contact associated with this onboarding ticket has Booked a Meeting where the Campaign is equal to any of “Onboarding Kickoff” → If a meeting has been scheduled we can exit the workflow. All is good. → If a meeting has not been scheduled we need to take the appropriate next steps to drive action. 10. IF meeting not schedule, send an automated reminder email which includes a link to the task in the onboarding plan to book the meeting. 11. Delay the workflow for 1 day. 12. Repeat the IF/THEN from step 9 to check if a contact associated with this onboarding ticket has Booked a Meeting where the Campaign is equal to any of “Onboarding Kickoff” → If meeting has been scheduled we can exit the workflow. All is good. → If meeting has not been scheduled we want to check if any action has been taken in our plan to determine the level of risk. 13. IF/THEN check if “Arrows Plan Progress” has any value. This indicates a customer has completed tasks in their onboarding plan. → If tasks have been completed we still need them to book their kickoff but they are engaged. → If no tasks have been completed AND they haven’t scheduled a call they are now “At Risk” 14. For “At Risk” accounts: → Set the “Account Health” property to 🟥 → Create a task for the ticket owner to enroll them in an “at risk” sequence. → Send an alert to Slack to increase visibility 15. For “Making Progress accounts: → Set the “Account Health property to 🟨 → Create a task for the ticket owner to enroll them in a meeting booking sequence. Effective onboarding builds momentum, if you can avoid “drag” between customers taking action, understanding the next step and your team's response when things get off track... You'll more effectively keep them in motion. Follow me and hit the 🔔 to steal another workflow next Tuesday! #hubspot #hubspottipsandtricks #customersuccess