Suggestions
Alyson Posey
Data Leader | Data Sorceress
Alyson Posey is a professional working at RxBenefits, Inc. with a background in data and technology.1 She is described as a collaborative leader with years of experience across engineering, data science, and tech.1 In her role, Alyson is known for being a thoughtful partner who strives to support her colleagues.1
Professional Experience
Alyson's current position at RxBenefits, Inc. appears to be in the field of Data Reliability Engineering, which aligns with her extensive background in data and technology.1 Her expertise likely involves ensuring the reliability, scalability, and efficiency of data systems within the company.
Skills and Expertise
Based on her professional profile, Alyson's areas of expertise include:
- Data science
- Engineering
- Technology leadership
- Business intelligence architecture
- Database architecture
- Team leadership
Contributions and Insights
Alyson is active in sharing her knowledge and experiences on professional platforms. She has posted about lessons learned from troublesome projects2, indicating her commitment to continuous improvement and knowledge sharing in her field. Additionally, she has emphasized the importance of data quality, noting that even AI cannot overcome poor data inputs.3
Professional Network
Alyson's LinkedIn profile (username: alyson-posey-02607624) serves as a platform for her to connect with other professionals in her field and share insights about data engineering and technology.1 Her presence on professional networks suggests she values industry connections and staying current with trends in her field.
It's worth noting that Alyson Posey's role as a Data Reliability Engineer at RxBenefits, Inc. showcases her specialized skills in maintaining and improving data systems, which is crucial in today's data-driven business environment.
Highlights
Lessons Learned from a Troublesome MINI: The Importance of Data Reliability
Several years ago, my husband and I bought a 5-year-old R57 MINI Cooper – a charming convertible that promised exhilarating drives. Little did we know the thrill of the drive would often be marred by mechanical woes. Barely a week after our purchase, it plunged into "limp mode," leaving us perplexed and disheartened. Our visit to the mechanic was a frustrating episode reminiscent of Charlie Brown's teacher's incomprehensible mutterings, with his "wah wa wa turbo charger wah wa". Turns out, some R57s are infamous for being a bit of a headache.
We got it fixed up, only for it to break down again a month later during a family visit. Cue the "fuel pump wah wawa wah" saga. Then, on a day out with friends, it conked out yet again, blaming it on the "wah waw a waw ah Heat pump." The MINI seemed determined to test our patience. Even after multiple repairs and assurances, our confidence dwindled with each breakdown.
We thought we'd given it enough TLC to take a two-hour trip, but nope. It ended up getting towed back home. That was the last straw. We sold it off after another round of repairs. Every time I hopped in, it felt like it was just waiting to break down again. I couldn't keep track of all the issues, it was beyond frustrating.
Now, how does this relate to Data Reliability, you ask? Picture the MINI's components as akin to the components of a decision support system. The turbocharger is like a coding glitch, the fuel pump represents flawed source data, and the heat pump symbolizes transforming data into user-friendly formats. But here's the kicker: no matter how much you try to fix it up, if the system keeps spitting out bad results, users lose faith in it. They might start out patient, but sooner or later, they're going to look for a better solution—whether it's calling in experts or ditching the system altogether.
In my experience, I've witnessed both failed and successful systems. Some of the failed systems were well-architected but suffered from execution flaws, bad data, or a failure to meet user needs. This resulted in frustrated end-users seeking alternative solutions. Conversely, successful systems often began with thorough discussions with end-users to identify existing challenges and requirements. By understanding the data and addressing issues early on, plans were devised to ensure data reliability. While some source data issues required collaboration with subject matter experts to refine the source data, others necessitated alternative approaches to provide users with reliable data.
Additionally, identifying a flexible subject matter expert with a solid use case for beta testing proved instrumental in validating the system's reliability. Once a successful use case was established, word-of-mouth endorsements helped build user confidence, paving the way for further system expansion and adoption.
I’m happy to share that I’m starting a new position as Data Reliability Engineer at RxBenefits, Inc.!
