Using Checklists to Boost Efficiency

I've tried the fancy productivity systems, but here's what works: This 3x5 notecard... Each evening, I sit down at my desk and write down the 3-5 highest impact to-dos for the following day. These are the "important" tasks that directly contribute to my long-term projects or goals. The list is pure—I specifically avoid writing down all of the miscellaneous urgent and unimportant to-dos (more on that later). In the morning, I sit down at my desk for my first focus work block and start at the top of the list, working my way down and crossing off the important items as I get through them. My primary goal is to cross each item off the list by the end of the day. I am intentionally conservative in the number of items I write on the list. It's usually 3, sometimes 4, and very rarely 5. I never want to end the day with open items, so being conservative helps me accomplish that (and get the extra rush from getting through more than I expected). As I go through the day, I stole an idea from Marc Andreessen to use the back of the card to write down and cross off any minor to-dos that I complete (the urgent or unimportant tasks that are not welcome on the front of the card). The process of writing and crossing off an item on the back of the card is a further boost of momentum, so I find it to be a worthwhile exercise. My notecard productivity system is painfully simple, but it's grounded in five powerful realizations: 1. 15 minutes of prep in the evening is worth hours the next morning. By setting out your priority tasks the night before, you eliminate any friction from having to decide what to work on. You hit the ground sprinting. 2. Important > Urgent. By tackling the important to start the day, you guarantee progress against the big picture projects and goals. If my day went to hell after that morning focus block (which it sometimes does with a 1-year-old at home!), it would be ok, because I know I've gotten through much of my important work. 3. Momentum is everything. Crossing important items off your list to start the day immediately creates a winning feeling that you keep with you. Success begets success. 4. Simple is beautiful. If you're spending time thinking about your productivity system, you're studying for the wrong test. That's movement for the sake of movement. You should be focused on progress. 5. Find what works for you. It used to stress me out that I didn't have a beautiful productivity system that would impress others. Then I realized that whatever works for me is the best productivity system. Identify how you operate and find the system that works for you. To get started, just buy a stack of simple 3x5 notecards and give it a shot. If you've ever been overwhelmed by productivity systems and advice, this is an approach to try. Follow me Sahil Bloom for more ideas like this in the future and join 800,000+ others who get these in my weekly newsletter: https://lnkd.in/esGsF85Q

Someone like ex-Air Force Thunderbird pilot Michelle “MACE” Curran has a checklist she goes through before taking her F-16 to the sky. And someone like CAPT Chris “Chowdah” Hill trains his ship to perform a set of tasks when he calls “battle stations”. If we’re smart, we also create a clear set of rules or steps our teams can follow to complete projects or to react to things that happen. But I found it interesting that just coming up with the steps to follow isn’t enough. You also need to clearly define how people will use the checklist, and I learned there are two paths to take, with pros and cons depending on the kinds of tasks. A READ-DO approach means you read the step, and then perform the task. This is how most of us follow a recipe when cooking something new. It’s how we build lego castles following the instructions. A DO-CONFIRM approach means you perform the task (usually from memory/practice) and then after pause to confirm that you’ve done it. Sounds similar, but the DO-CONFIRM approach is better when you have a team working together and when the overall checklist needs to be completed quickly. Imagine an emergency team responding to a situation. You don’t want everyone standing around as someone reads off step by step what to do. You want everyone jumping into action and then calling out what has been completed while someone confirms all the things are getting done. Besides speed, a high-performing team is also likely to jump ahead and potentially make more mistakes in a READ-DO format because they get bored or antsy waiting for the next step. What format works best for your team or the task you’re defining? Make sure to focus not just on the steps, but on how the steps or recipe should be followed.

Too often sales managers and VP's 'Set Expectations' but then are SHOCKED when people don't follow through. More often than not it's because they skipped some VERY important steps when it comes to rolling out anything new. So for change management to really occur, any new process, these are the steps you have to follow. 1. Sell vs Tell - Sell WHAT you want done. Tell the story. Tell the impact. Sell the WHAT, not just tell it. 2. Explain the how - Aka WGLL (wiggle aka what good looks like) - Here is what good looks like. 3. Teach and Train - Don't just assume people know how to do it! You have to actually teach it step by step. 4. Get Agreement and Commitment - You need direct agreement back saying 'yes I will do this thing and I feel confident i can do this thing' 5. Do it together - The first few weeks/iterations ideally are done as a group. Get the momentum going, get the questions out of the way, etc. 6. Inspect and Follow Up - Don't let weeks go by and THEN check in. That needs to be done before something is due AND after. Don't wait for the miss. 7. The 4 R's - Recognize (If they did it, recognize them for it!) Reward (same idea, what does it unlock) Repercussion (If they didn't what are the repercussions) Repeat/Repetition (Keep it going. Review, Update, etc) This is change management. So if there are certain things your team is supposed to be doing but arent... Go to these 7 steps. Did you miss something?

This one checklist made my life 10x easier (Save hours later by following these steps now!) Over the last 22 months, I’ve attended 184 walkthrough meetings. Trial. Error. Frustration. Fixes. And through all of that, I created this simple system. A checklist that every auditor should follow after the walkthrough ends. If you’re tired of scrambling for screenshots, losing notes, and chasing follow-ups days later, Save this post. Share it with your team. Use it every time. Post-Walkthrough Checklist: The SOP I swear by 1. Segregate your screenshots (Immediately) - Use Windows + Print Screen to capture quickly. - Create a new folder right after the meeting using this format: [Date]_[Control_ID]_[ControlName]_[AuditName] - This makes it easy to find everything later. 2. Store in two places - One local folder on your laptop - One shared folder (e.g., Teams) so others don’t need to ping you 3. Summarize your notes - Right after the meeting, take 5–10 minutes to clean up your notes. - Capture who said what, any key clarifications, and system flows. 4. Save notes smartly - Again one local, one shared. - Use the same naming format for consistency. 5. List out all follow-ups in one place - Don’t rely on memory. - If something needs clarification or additional evidence, document it immediately. 6. Assign owners and due dates - Use a tracker to assign each follow-up to a control owner with a clear timeline. - This alone will save you days of back-and-forth. 7. Update your main control tracker - Capture the status of the walkthrough and all pending items. - If your team doesn’t have a control tracker, create one. (And if they do make sure you’re using it daily.) Bonus: I personally keep a tracker with separate tabs for each audit I’m working on. Every control I’m assigned gets listed with deadlines, dependencies, and current status. This isn’t just a checklist. It’s a habit. Follow it after every walkthrough and your future self will thank you during wrap-up week. Have your own post-walkthrough system? Drop it below! I’d love to see how others do it.

Critique this (real) team's experiment. Good? Bad? Caveats? Gotchas? Contexts where it will not work? Read on: Overview The team has observed that devs often encounter friction during their work—tooling, debt, environment, etc. These issues (while manageable) tend to slow down progress and are often recurring. Historically, recording, prioritizing, and getting approval to address these areas of friction involves too much overhead, which 1) makes the team less productive, and 2) results in the issues remaining unresolved. For various reasons, team members don't currently feel empowered to address these issues as part of their normal work. Purpose Empower devs to address friction points as they encounter them, w/o needing to get permission, provided the issue can be resolved in 3d or less. Hypothesis: by immediately tackling these problems, the team will improve overall productivity and make work more enjoyable. Reinforce the practice of addressing friction as part of the developers' workflow, helping to build muscle memory and normalize "fix as you go." Key Guidelines 1. When a dev encounters friction, assess whether the issue is likely to recur and affect others. If they believe it can be resolved in 3d or less, they create a "friction workdown" ticket in Jira (use the right tags). No permission needed. 2. Put current work in "paused" status, mark new ticket as "in progress," and notify the team via #friction Slack channel with a link to the ticket. 3. If the dev finds that the issue will take longer than 3d to resolve, they stop, document what they’ve learned, and pause the ticket. This allows the team to revisit the issue later and consider more comprehensive solutions. This is OK! 4. After every 10 friction workdown tickets are completed, the team holds a review session to discuss the decisions made and the impact of the work. Promote transparency and alignment on the value of the issues addressed. 5. Expires after 3mos. If the team sees evidence of improved efficiency and productivity, they may choose to continue; otherwise, it will be discontinued (default to discontinue, to avoid Zombie Process). 6. IMPORTANT: The team will not be asked to cut corners elsewhere (or work harder) to make arbitrary deadlines due to this work. This is considered real work. Expected Outcomes Reduce overhead associated with addressing recurring friction points, empowering developers to act when issues are most salient (and they are motivated). Impact will be measured through existing DX survey, lead time, and cycle time metrics, etc. Signs of Concern (Monitor for these and dampen) 1. Consistently underestimating the time required to address friction issues, leading to frequent pauses and unfinished work. 2. Feedback indicating that the friction points being addressed are not significantly benefiting the team as a whole. Limitations Not intended to impact more complex, systemic issues or challenges that extend beyond the team's scope of influence.

Ever tried to change a tire while the car's still moving? That's what implementing organizational change can feel like for you and your team. We've all been there. 😅 Pushing through changes without a clear strategy, hoping sheer determination and long nights would be enough. But nope. The change initiative ended in confusion, resistance, or maybe didn't make it across the finish line before everyone abandoned ship. I've been there—from implementing organization wide learning programs to updating team policies. And let me tell you, without a roadmap, it's chaos. 🌪️ ---From Chaos to Smoother Sailing---- Enter the Knoster Model for Managing Complex Change. It's like GPS for navigating the treacherous waters of change management. This model has been hanging in my office for the last 10 years, serving as a visual cue to ensure I have all 5 elements covered before taking on change initiatives. ----Here's the Model---- Vision + Skills + Incentives + Resources + Action Plan = Successful Change 🔹 Vision: Where we want to go 🔹 Skills: What we need to know 🔹 Incentives: Why we should care 🔹 Resources: What we need to use 🔹 Action Plan: How we'll get there -----The Impact of Missing an Element---- 🚫No Vision? Confusion reigns 🚫Lacking Skills? Anxiety spikes 🚫Forget Incentives? Resistance grows 🚫Skimp on Resources? Frustration builds 🚫Skip the Action Plan? False starts abound Over the years, this model has become my diagnostic tool. When I hear confusion about where we're going or what we're trying to achieve, I immediately know I haven't been clear on the vision element. 🚩 It's like a red flag waving, telling me to step back and refocus on communicating our goals and business objectives. Similarly, when I notice people are confused about how they're going to meet the vision, it's a clear sign that I haven't properly set them up for success with the right skills. This realization always prompts me to pause and reassess where I can improve. 🔄 It's a simple framework and can also be used as a self-assessment tool. Now, it's your turn to put this model into action: Think about a change initiative you're currently planning or struggling with. Which of the five elements needs your attention most? Is your vision crystal clear? Are your team's skills up to par? Which element are you excellent at?

Every Sunday I take 3 actions that require less than 5 minutes but improve my efficiency tenfold heading into a new work week. 1️⃣ Review my to-do list. I’ll often add items to my to-do list throughout the week. By end of Friday they should (hopefully) be detailed enough to action on them, but on Sunday I’ll sort the to-do list so I can select which 2-3 items I’ll be prioritizing for the day or week. 2️⃣ Close my tabs. I’ve finally accepted that I’m never going to remember why I opened all those tabs in the first place. I call it declaring tab bankruptcy. A fresh Google Chrome window to kick off the week is always a good start. 3️⃣ Set my intentions. Knowing what I have going on in a given work week, what is actually feasible? If it’s a short work week or a particularly meeting-heavy week, I’ll accept that it’s not a week when I’ll have enough focus time to get through everything I think I need to do. Low effort, high impact.

The monitor walked into our site and found 3 GCP violations in 10 minutes. My stomach dropped. Not because we were careless. But because we thought we were compliant. Here's what I learned that day: Good intentions aren't enough in clinical research. You need systems. After 10+ years in this industry, I've seen the same violations destroy careers and compromise trials. Let me break down the 7 most common GCP violations—and how to avoid them: 1️⃣ Inadequate Informed Consent ↳ The risk: Invalid subject data & regulatory penalties ✅ The fix: Always use the latest IRB-approved form & document consent properly 2️⃣ Protocol Deviations ↳ The risk: Compromised data integrity ✅ The fix: Train staff thoroughly & document all deviations immediately 3️⃣ Incomplete Source Documentation ↳ The risk: Audit findings & data loss ✅ The fix: Record data in real-time & maintain source-to-CRF consistency 4️⃣ Poor Investigational Product (IP) Accountability ↳ The risk: Patient safety issues & protocol noncompliance ✅ The fix: Log all IP receipts, dispensation, and returns accurately 5️⃣ Failure to Report Adverse Events (AEs) ↳ The risk: Regulatory noncompliance & patient risk ✅ The fix: Train team on AE reporting timelines and definitions 6️⃣ Inadequate Delegation of Duties ↳ The risk: Tasks performed by unqualified staff ✅ The fix: Maintain a current Delegation Log & verify credentials 7️⃣ Missing or Expired Regulatory Documents ↳ The risk: Site noncompliance ✅ The fix: Set calendar reminders & use a document tracker The truth is These violations aren't about being perfect. They're about being prepared. Every single one is preventable with the right systems and training. But here's what most sites miss: ➡️ Preventing GCP violations starts with training, checklists, and a compliance-first culture. Not fear. Not perfection. Just consistency. If you're running trials without these systems—you're not protecting patients. You're hoping nothing goes wrong. And hope isn't a compliance strategy. What's the most common GCP violation you've seen at sites? Drop it below. Let's learn from each other. Follow Rudy for more real-world clinical research insights. #clinicalresearch #GCP #compliance #clinicaltrials #patientSafety #regulatoryaffairs #CRA #CRC

I’m often asked how I prep for customer calls. Here’s the 5-point, 15-minute checklist I’ve been using over the last decade before every customer meeting: 1/ Look up all attendees on LinkedIn Goal here is to know who you’re talking to and where they’ve worked. Pro-tip is to find 1 commonality with each person to quickly build rapport (ie college, living location, previous employer, etc.) 2/ Browse their website This is the most obvious thing that is not done enough. Go to their website and learn about their products and value prop. Jot down a few of their key customers to reference. See if they have any unique channels like a partner program. This one is a no-brainer that is skipped way too much! 3/ Study their LinkedIn company page I’ve found that LinkedIn company pages are full of unique insights you can’t find elsewhere. They have the most accurate employee counts, can give you a pulse on recent posts, and provide an up-to-date company mission in a few short lines. 4/ Find the latest news via Google News Do a Google News search for the company. Heading into a meeting, I’ve found huge nuggets here like a CEO change, a recent acquisition, or even controversies to steer clear of. 5/ Understand their market via a competitor search Do a simple search for [company name] competitors. This will give you a good sense of the landscape and who they are competing against. And 2 bonus points if you're meeting with a public company: 6/ Look up their stock ticker on Google Finance This will give you a real-time view into the company financials. I like to zoom out to 1 or 5 year performance, and do a quick glance into the “news” section for insight on recent earnings. 7/ Understand the company history via Wikipedia This one is not used enough, but there are tons of juicy details you can find on Wikipedia pages. Almost a mini-history lesson on a company. What else do you do to prep for your customer meetings? #sales #salesenablement #learning 

New fiscal year, new big plans. We all love a bold strategy, but let’s be real —most grand initiatives fail, not because the idea was bad, but because something crucial was missing. Years ago, I got this checklist, and I still use it to keep change management and execution on track: ✨ Vision – Without it, confusion reigns. People need to know why change is happening and what success looks like. ✨ Skills – A brilliant idea without the right skills just leads to anxiety. If your team isn’t equipped, fear of failure will creep in fast. ✨ Incentives – No motivation, no movement. People need a reason to embrace change - whether it’s recognition, rewards, or a sense of purpose. ✨ Resources – The best plan in the world won’t work if you don’t have the right tools, time, or support to make it happen. ✨ Action Plan – Without clear steps, timelines, and accountability, momentum stalls. A vague plan is just a wish. As you roll out your big initiatives, check if you’ve got all five elements covered. And if one is missing - what’s your workaround? Not everything will be at 100%, so what trade-offs are you making to keep things moving? A simple but powerful way to kick off the right conversations. #Leadership #Strategy #Execution #ChangeManagement #Growth #BusinessSuccess #NewFiscalYear