<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jared S. Taylor on Medium]]></title>
        <description><![CDATA[Stories by Jared S. Taylor on Medium]]></description>
        <link>https://medium.com/@jaredstaylor?source=rss-75a03d310acd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xCWM1-O8LGjAdKGFN0HFzg.jpeg</url>
            <title>Stories by Jared S. Taylor on Medium</title>
            <link>https://medium.com/@jaredstaylor?source=rss-75a03d310acd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:08:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaredstaylor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Our Approach To Provider Directories]]></title>
            <link>https://medium.com/blochealth/our-approach-to-provider-directories-efa329bdaf54?source=rss-75a03d310acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/efa329bdaf54</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[credentialing]]></category>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[provider-enrollment]]></category>
            <category><![CDATA[payer]]></category>
            <dc:creator><![CDATA[Jared S. Taylor]]></dc:creator>
            <pubDate>Thu, 06 Feb 2020 21:12:58 GMT</pubDate>
            <atom:updated>2020-02-06T21:12:58.971Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KoMNi-W0FmZtSEj1.jpg" /></figure><p>*THIS STORY IS BY ADRIENNE BOLGER, CTO OF BLOCHEALTH</p><p>An astute social media user asked BlocHealth a question recently:</p><p>“How are you going to overcome the directory issues. That has been our biggest issue. I have worked on all sides of Credentialing and currently address is still a huge problem.”</p><p><strong>What is the Directory Problem?</strong></p><p>The Directory Problem, as I call it, is the general problem of maintaining up-to-date contact information for all health care practitioners and other contacts a credentialer needs to deal with in order to get someone credentialed in health care. Insurance companies, hospitals, and CVOs all have some variation of the directory problem for different parts of their businesses.</p><p>There are 2 parts to the problem. One is general, one is specifically obnoxious for credentialers. If a business asks for your current address, you can give it to them, and a business can mark when the data was last updated and be sure it is accurate. This is generally annoying, but at least possible. Part 2 is that credentialers often have old data handed to them as current data because credentialers have to track down and verify old work histories and practices for new hires. A new hire’s resume might be updated into the system on Jan 1, 2020, but if that resume has 10-year-old contact information on it for retired peer references, it hardly matters how recent the resume is. This makes maintaining accurate data over time expensive because it has to be re-checked every time it is entered, by everyone who receives it.</p><p><strong>(Partial) Solution #1: Technology</strong></p><p>At BlocHeatlh, we plan on a 3-pronged approach in our technology for fixing “the directory problem.”</p><p>Our first strategy is to rely on existing data to build out our directory as much as possible- this involves pulling data (with it’s known possible inaccuracies and limitations) from many sources: everywhere from United States national government databases to Google maps, and also from users’ resumes and website crawlers to get the latest information. It’s not going to be perfect, but it is a start, and better than starting from nothing.</p><p>It should be noted that this strategy, while not requiring a lot of cash outlay, does require the technical sophistication and infrastructure to merge data from multiple sources. Technology will not solve all your problems, and sometimes it can make them worse because of…</p><p><strong>(Partial) Solution #2: Breaking Data Silos</strong></p><p>Data silos are a big part of why the directory problem exists. Every organization is fighting the directory problem separately, and keeping their solutions to themselves. BlocHealth’s 2nd strategy is sharing public directory data for common business resources like insurance carriers , brokers, and hospitals among as many users as possible to distribute the update burden. There are some nuanced technical requirements to doing this. For example, like Yelp, verified organizations should be able to claim and manage profiles from such a directory, but like Wikipedia, all users should also be able to easily maintain and request updates to shared data, so all users can benefit. Technical organizations can learn a lot from how organizations like Wikipedia continue to function as a shared data resource for many people. Auditing requirements also must be in place so the provenance of data is tracked.</p><p><strong>Solution #3: Pro-actively incentivize individual users whose data you need.</strong></p><p>The 3rd strategy addresses what most people are talking about when they say the ‘directory problem’: individual health care practitioners’ information. This kind of information is private: it can’t be maintained in a public format like Wikipedia or YellowPages.com.</p><p>Organizations have the most problems getting this kind of information updated because they are (1) maintaining the information only for themselves in a silo (2) getting it updated reactively, and (3) using a ‘stick’ instead of a ‘carrot’. The following scenarios are common in healthcare:</p><p>A practitioner is told, “You must update your address and fill out this entire application exactly correctly (which takes an hour) or we will withhold your insurance payment approval.”</p><p>A practitioner is told, “You must update your phone number or our hospital will not renew your privileges.”</p><p>This, does not, to put it mildly, engender good will towards health care business administrations.</p><p><strong>Instead, BlocHealth recommends that you recognize the time spent and the personal data submitted by practitioners for the valuable commodity that they are.</strong></p><p>If you’re a technical organization, design all directory technology to need only the minimum updates and prioritize making updates VERY FAST. A great new technology in this area is mobile-friendly websites that users are prompted to visit via a one-time secure link sent via SMS/text message on their smartphone. The process is seamless, has great response rates, and is fast for updating for everyone involved. <br>Even if you aren’t a hi-tech organization, you can still proactively incentivize practitioners to update data by giving them some value in return. In BlocHealth’s case, our platform offers a resume generator, a digital peer reference process, a common application, and other features designed to save the professional time by keeping their directory information up to date. For your organization, it might be as simple as enacting a process where updated contact information gets used for credentialing, HR updates, and a yearly birthday card. Get creative!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efa329bdaf54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blochealth/our-approach-to-provider-directories-efa329bdaf54">Our Approach To Provider Directories</a> was originally published in <a href="https://medium.com/blochealth">BlocHealth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CAQH Passwords on Application forms: A Halloween Horror Story]]></title>
            <link>https://medium.com/blochealth/caqh-passwords-on-application-forms-a-halloween-horror-story-6407ab62ae52?source=rss-75a03d310acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6407ab62ae52</guid>
            <category><![CDATA[hospital]]></category>
            <category><![CDATA[credentialing]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[healthcare-technology]]></category>
            <category><![CDATA[provider-enrollment]]></category>
            <dc:creator><![CDATA[Jared S. Taylor]]></dc:creator>
            <pubDate>Thu, 06 Feb 2020 21:11:05 GMT</pubDate>
            <atom:updated>2020-02-06T21:11:05.673Z</atom:updated>
            <content:encoded><![CDATA[<p>*THIS STORY IS BY ADRIENNE BOLGER, CTO OF BLOCHEALTH</p><h3>Happy Halloween! Today, I’m here to tell you a story so awful, so nightmarish that it will have anyone who has ever worked remotely near an IT department sleeping with the lights on. No, it’s not “IT Chapter Two” or “Get Out”. Instead, this story is about how a well-intentioned organization caused physicians to hand out their personal account passwords like Halloween candy corn, and their employers joined right in to help.</h3><p>Once upon a time, there was (and still is) a nonprofit called the CAQH, set up by insurance companies to try and reduce paperwork. They created a product called CAQH ProView that “… eliminates duplicative paperwork with organizations that require your professional and practice information for claims administration, credentialing, directory services, and more.” Their goal was to reduce duplicated paperwork for providers and insurance companies, and the future was looking bright.</p><p>But, darkness fell across the land. Physicians were expected to enter data into a long, complicated form, and when a physician made a mistake, the insurance carriers who used the CAQH used incomplete or incorrectly filled out forms as a reason to delay or deny coverage approvals. A mistake on a CAQH profile could cost a physician months in lost revenue, making such mistakes an unacceptable loss.</p><p>Physicians and their employers turned to the champions of light and order: their own medical staff offices and outsourced credentialing specialists who were experts at filling out the paperwork exactly right and guaranteeing proper processing, but now there was a problem: these experts and paperwork ninjas could collect data from physicians, but CAQH ProView profiles were supposed to be attested by the physician. The 3rd party experts had no ability to access the data with their own unique user-names and passwords as this is not the type of access allowed by the current structure of CAQH. Practice managers ran into trouble because physicians many times work at more than one practice. Each of these practices would then compete for control of the data contained in a physician’s CAQH profile. So institutions nation-wide struck a deal with the devil and started sending out employment and medical staff application forms that look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NyklrytH6tWw5t0d.png" /></figure><p>The deal was struck, and it still stands today: if payers won’t accept information that actual physicians can reasonably provide with their time and knowledge available, then payers aren’t going to get the application filled in by the actual physician.</p><p>This is the stuff of IT nightmares: once a password is out there, anyone from the organization who can see the application can see it or use the password. What’s more, because it’s being shared between multiple people who are responsible for the account, it can never be changed, lest the office manager becomes unable to update it. God forbid the provider used that password on some other account as well, as is still common (even if not recommended). If the CAQH is compromised, and they try to re-secure their own user base by resetting the passwords of all their users (a common strategy after a known data breach), they will destroy the workflow of thousands of people.</p><p>Horror stories like this are often used to teach lessons, so what can other tech companies and IT departments in healthcare do to avoid getting their souls stolen in such a deal? Well, one is usability: if you make a form so difficult to fill out that 95% of your intended users do it wrong, that’s on you, not on your users. My boss from my first internship taught me a hard lesson in design that’s stuck with me: “<strong>The user is never the stupid one.” </strong>Even more so in this case, since your intended user probably has an MD!</p><p>The second lesson is a little more sophisticated, but can be summed up by a quote from a smart former co-worker of mine who runs a blog on software design: “<strong>Remove the word ‘user’ from your vocabulary and replace it with something more specific”. </strong>Did you design for the office staffer, the physician, the manager, the employer, and the CVO contractor? All of them count as the user, and all of them get paid to get s*** done, whether or not it means using your software in the way the instruction manual states.</p><p>Happy Halloween! May your code be free of bugs and devils!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6407ab62ae52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blochealth/caqh-passwords-on-application-forms-a-halloween-horror-story-6407ab62ae52">CAQH Passwords on Application forms: A Halloween Horror Story</a> was originally published in <a href="https://medium.com/blochealth">BlocHealth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who puts the “Primary” in “Primary Source Verification” anyway?]]></title>
            <link>https://medium.com/blochealth/who-puts-the-primary-in-primary-source-verification-anyway-a9df03bc0c62?source=rss-75a03d310acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9df03bc0c62</guid>
            <category><![CDATA[credentialing]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[medicare]]></category>
            <category><![CDATA[joint-commission]]></category>
            <dc:creator><![CDATA[Jared S. Taylor]]></dc:creator>
            <pubDate>Sat, 31 Aug 2019 20:41:04 GMT</pubDate>
            <atom:updated>2019-08-31T20:41:04.582Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hirx3C42Y7PUjMtqmGQBSQ.jpeg" /></figure><p><strong>*THIS STORY IS BY ADRIENNE BOLGER, CTO OF BLOCHEALTH</strong></p><p>TL;DR: Primary Source Verification in credentialing is the idea that particular information, (like your college major and the date you graduated from college) must be confirmed as coming from a particular primary source (like the college that granted you the degree). It sounds logical… until it isn’t. This trilogy of articles presents BlocHealth’s proposed way of accomplishing the same goals as of today’s Primary Source Verification processes.</p><p>Article 1 (this article) summarizes how the term is actually used in the healthcare credentialing space. Article 2 will discuss PSV usage in today’s digital world.</p><p>Article 3 will cover how BlocHealth intends to extend the definition of PSV with the next generation of technology: the blockchain.</p><p><strong>About the Author</strong></p><p>Before I became BlocHealth’s Chief Technology Officer (CTO), I had to learn about healthcare credentialing. I quickly ran into the term “Primary Source Verification” and got frustrated with the vagueness of the phrase. This article summarizes how the term is actually used in the healthcare credentialing domain and how that turned out to be surprising to me, a stranger with an engineering background.</p><p><strong>What is Primary Source Verification?</strong></p><p>According to the National Association of Medical Staff Services (NAMSS), someone who performs Primary Source Verification: Obtains and verifies a credential directly from the original issuing entity</p><p>In general, PSV is the process of verifying information about a healthcare professional by asking the primary source of information that either initially recorded or generated certain information. Employers perform PSV when considering potential employees. Health insurance companies also perform PSV when they decide whether or not they will allow a healthcare professional to bill their members for services rendered. PSV at its heart is about professional standards and fraud prevention. Is that person in scrubs who is about to perform a septal myectomy on your grandma qualified to do so? How do you know? PSV is one way of trying to put these fears to rest.</p><p>What’s a good primary source? It can be a ‘who’ or a ‘what’. Obvious examples of primary sources include a former employer, the U.S. Federal Government, colleges, medical boards, and other organizations like the American Red Cross. Organizations or people that issue licenses or numbers and maintain records to go with them are basically all primary sources of trust. A primary source is almost never the professional themselves because primary sources are used as a cross-check for fraud prevention. However, a healthcare professional can be a primary source for other professionals: a peer reference letter can be considered a primary source verification.</p><p><strong>The Problem with “Primary”: It Isn’t.</strong></p><p>Organizations that issue licenses to increase trust and to decrease fraud across medical professions sound great, but PSV isn’t actually this straightforward. My engineer brain hit a wall when I learned that “primary” in the credentialing field… just isn’t primary! It can also actually mean actually a “trusted secondary” source. A “primary” source can be an originator of information… or a designated collector of information… or a paid 3rd party. For example, the American Medical Association sells several software and database products that are aggregates of other primary sources of information. Because the AMA is a trusted, well-regarded organization and they verify with these other primary sources, paying the AMA for specific profile data is considered “primary source verification” by the standards of some governing bodies of hospitals… but not all of them.</p><p>So who gets this special “trusted secondary” status? It depends on history, politics, and a few other things. Engineers commonly see standards as checklists. In the IT world, for example, various security compliance rules and ISO standards are presented as a set of tasks to accomplish. If you do X, Y, and Z, and someone checks your work, you are “trusted.” You can be labeled as a secure website domain and issued a certificate by going through an audit process. This process is available to anyone. For a real-world example, go find your nearest electronic power cord brick and look for a “CE” stamp of approval on it. That standard, while it requires work to get, is published, and available to any organization that wants to do the work. If you design a power cord not to catch fire, and you run a set of tests showing the power cord does not catch fire, you can be awarded a “trusted” certification.</p><p>Do the “primary” or what we’ll call “trusted secondary” sources in credentialing follow this kind of process to achieve trust? In a word, no. Mostly, it’s a social contract based on the perception of trust. Sometimes it’s a non-profit. Sometimes it’s a 3rd party software that’s been paid by the original organization to be an official digital or paperwork agent. Sometimes it’s the other way around: a company can be the trusted representatives of a primary source because they have paid money for the copy of trusted data. There are rules and standards, but they aren’t applied evenly. This kind of contract makes it easy for existing trusted organizations, like medical schools, to fall back on their historical status to be trusted, but difficult for newer organizations to gain trust quickly.</p><p>As a CTO, I see this as a business problem for software companies like BlocHealth. That’s likely not interesting to you as the reader, but what you may find interesting is that this is also a general problem for those in healthcare trying to enhance standards of care in newer industries and streamline existing processes with technology in any way. Just to note a few of the people looking to improve our world, at BlocHealth, we’ve talked to people and organizations who want everything from:</p><ul><li>Better standards for hiring in the booming business of urgent care centers</li><li>Faster processes for credentialing telehealth providers</li><li>Increased education standards for RNs.</li><li>The ability to reduce physician and advanced practitioner paperwork load to decrease burnout</li></ul><p>These people all run into a roadblock with the current methods of determining what counts as ‘primary’ sourcing because who can get that status is a political process. How can these newer organizations update the existing standards of care? What will make them “primary” or “trusted secondary” sources of information? And how can they supply credentials in a digital world when the current method of becoming ‘trusted’ requires you to exist for 100 years or pay money to someone who is?</p><p>The issue of who to trust, and how to prove you can be trusted is as difficult as it ever was, but BlocHealth has some thoughts on that as well in part 2 of this series.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9df03bc0c62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blochealth/who-puts-the-primary-in-primary-source-verification-anyway-a9df03bc0c62">Who puts the “Primary” in “Primary Source Verification” anyway?</a> was originally published in <a href="https://medium.com/blochealth">BlocHealth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Free Time Can Have A Higher ROI Than Meetings, Here’s Why…]]></title>
            <link>https://medium.com/@jaredstaylor/free-time-can-have-a-higher-roi-than-meetings-heres-why-1f63f0a44f9a?source=rss-75a03d310acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f63f0a44f9a</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Jared S. Taylor]]></dc:creator>
            <pubDate>Fri, 28 Dec 2018 15:41:51 GMT</pubDate>
            <atom:updated>2018-12-28T15:41:51.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3SXD0RkFH2uwq_ca_qzsKA.jpeg" /></figure><p>Raise your hand if you like burning money. Now raise your hand if you have multiple meetings per day, month and year. There’s a good chance your hand was up for the second question and not the first, but isn’t that odd? People hate to lose money, and yet many employees and managers consistently engage in holding meetings that they believe are worthwhile. The truth is, many people like to think they’re busier than they actually are. Meetings are the perfect scapegoat. Most meetings can happen via a quick call, Slack message or email and yet, most get pushed into a long, in-person meeting. It’s a HUGE problem.</p><p><strong>THE STATISTICS</strong></p><ul><li><strong>25 Million</strong> meetings occur per day in the U.S.</li><li><strong>$37 Billion </strong>per day is spent on unproductive meetings in the U.S.</li><li><strong>15% </strong>of an organization’s collective time is spent in meetings</li><li><strong>50%</strong> of upper management’s time is spent in meetings</li><li><strong>35%</strong> of middle management’s time is spent in meetings</li></ul><p>SOURCE: <a href="https://www.themuse.com/advice/how-much-time-do-we-spend-in-meetings-hint-its-scary">https://www.themuse.com/advice/how-much-time-do-we-spend-in-meetings-hint-its-scary</a></p><p>The picture of a $100 bill being burned begins to make more sense after digesting the above statistics. Small, mid-size and large organizations need to seriously look at how much time is being spent on meetings. Then, they need to take a look at how many meetings could be considered unproductive. There will be times where in-person meetings are 100% necessary and can be a great team builder, but only when utilized correctly.</p><p><strong>QUESTIONS TO ASK BEFORE PLANNING A MEETING</strong></p><ul><li>Is this a bad time?</li><li>Is the meeting relevant?</li><li>Could the same information be absorbed with a quick email, phone call or Slack message?</li><li>Is this worth everyone’s time?</li><li>Can it be optional?</li></ul><p><em>Is this a bad time?</em></p><p>The chances of this being true are very high. I remember early on in my career being very busy trying to land new clients in my sales role. As many people know, sales is a very time intensive role. Cold calls, lead follow-ups, CRM data input, email campaigns, marketing plans and more are all things that need to be incorporated into one’s day-to-day to be successful in that type of role. While I was trying to land new clients, management was always trying to push different types of meetings on me several times per day (usually 2–4 meetings per day, most not worthwhile). I expressed my frustration multiples times and like many employees, my perspective on the matter was not fully digested by management. The worst part is that there were many occasions where I had a lot on my plate, only to see that a meeting was scheduled and my day derailed by unproductive meetings.</p><p><em>Is the meeting relevant?</em></p><p>In my opinion, 90% of meetings are not relevant. Recaps, multiple training sessions, strategy planning, etc. usually sound more important than they actually are. Is a 30-minute meeting going over team sales KPI’s necessary, when an email with the details that can be digested in 5-minutes would suffice?</p><p><em>Could the same information be absorbed in a quick email, phone call or Slack message?</em></p><p>Again, the answer here is YES a majority of the time. If some information is super private, then wait for a one-on-one review or use part of a more important meeting to discuss it.</p><p><em>Is it worth everyone’s time?</em></p><p>As a manager, try to quickly put yourself in your co-workers’ shoes. Try to visualize if this meeting is a need or a want.</p><p><em>Can it be optional?</em></p><p>Typically, when a meeting is considered optional, most employees will not attend. If you think for a second that a meeting could be optional, it is probably better to not have it at all. Send an email and be done with it.</p><p><strong>FINAL THOUGHTS ON MEETINGS</strong></p><p>Meetings should be eliminated from your day-to-day. If a meeting is ABSOLUTELY necessary, try to conduct it in a 15-minute time slot. If you can’t, chances are it’s not worth everyone’s time or yours! Meetings take a lot of time to plan, organize and create the proper discussion points. Think of what the time saved by eliminating meetings will mean for your ROI and employees’ well-being. We live in a business climate that demands more for less from employees and yet, many companies stick to that ideology while giving employees less time to do more work. Fewer meetings = more time and potentially more results. Make 2019 and beyond be the years that meetings begin to dwindle in quantity and increase in quality.</p><p>Fewer meetings, more results, happier employees…</p><p><strong>REPLACE UNPRODUCTIVE MEETINGS WITH FREE TIME</strong></p><p>Free time is better than unproductive meetings. When’s the last time you let one of your employees work on something company-related that TRULY interested them? Although many organizations claim they want their employees to be creative, the truth is that most of these organizations stifle creativity by barking out orders. When employees get to work on things that interest them, they become more invested in being creative and working harder. Try it. Essentially, it is allowing employees to be entrepreneurial without any of the risks. Google famously followed a “20% time policy.” This allowed employees to work on things that interested them. Who knows, maybe if Facebook hired the founder of WhatsApp years ago and allowed him to follow a 20% time policy, WhatsApp might have been created in-house at Facebook, resulting in the company saving close to <strong>$20 Billion</strong>.</p><p>Start small by giving employees free time starting at 2:55 PM through the rest of the day on a Friday to work on things that interest them. The only way to discover the ROI on this is to test, adjust and continue to test it. Studies have shown that 2:55 PM to EOD tends to be an unproductive period for employees (even more so if you take into account the excitement of the weekend approaching that occurs on a Friday).</p><p>SOURCE: <a href="https://www.fastcompany.com/3012479/255-pm-when-productivity-dies">https://www.fastcompany.com/3012479/255-pm-when-productivity-dies</a></p><p>Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f63f0a44f9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>