<?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 Tanaka Makoni on Medium]]></title>
        <description><![CDATA[Stories by Tanaka Makoni on Medium]]></description>
        <link>https://medium.com/@tamakoni?source=rss-fe2397a00e5c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qdMNvWJ2AJfsytcGXR_iJQ.jpeg</url>
            <title>Stories by Tanaka Makoni on Medium</title>
            <link>https://medium.com/@tamakoni?source=rss-fe2397a00e5c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:48:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tamakoni/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[A Summer on the Achieve Team]]></title>
            <link>https://medium.com/strava-engineering/a-summer-on-the-achieve-team-dabed37298f7?source=rss-fe2397a00e5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/dabed37298f7</guid>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[strava]]></category>
            <dc:creator><![CDATA[Tanaka Makoni]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 16:01:02 GMT</pubDate>
            <atom:updated>2026-09-30T16:01:02.658Z</atom:updated>
            <content:encoded><![CDATA[<p>As a subscriber on Strava, a lot of value comes from access to the Progress tab which is Strava’s home for tracking activity metrics, goals and performance over time. This summer, as a Software Engineering intern, I worked with the team behind the Progress Tab to enhance this surface to answer a specific question: how much of that experience could move beyond the app itself, out onto the other iOS surfaces athletes glance at all day?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*98w2jI7fouRw4GE4daNezA.png" /><figcaption>Picture of me and my mentor</figcaption></figure><h3>Getting Strava Off the Screen: Widgets</h3><p>Today Strava ships goal and streak widgets for the home screen. My work this summer centered on extending that ecosystem to new widget families in line with iOS’ latest updates. I worked on building lock screen widgets, a new performance prediction widget, and bringing widget support to the Apple watch app.</p><p>Three things motivated the investment.</p><ul><li><strong>Expanding presence</strong> — getting Strava’s metrics in front of athletes without asking them to open the app.</li><li><strong>Subscriber value</strong> — surfacing the kind of data (goal progress, performance predictions, streaks) that makes a subscription feel worth paying for.</li><li><strong>Active moments</strong> — turning a passive glance into nudges for users to be more active.</li></ul><h4>What a widget actually is</h4><p>A widget is a small, glanceable UI extension that lives outside your app. It shows you something at a glance without making you open the app.</p><p>But it’s also a separate program with its own life. It can’t see inside the app, can’t reuse the app’s credentials, and can’t reach the app’s data. Nor does it run continuously. Instead, it renders a snapshot of your data, hands that snapshot to the system, and goes back to sleep. The operating system decides when to wake it up and ask for a fresh version, and it doesn’t hand out unlimited wake-ups.</p><p>So the real engineering problem is: how do you get accurate, current data into a small program that’s asleep most of the time and can’t directly retrieve it from the app?</p><p>Apple’s answer is WidgetKit, a single framework that now spans the home screen, the lock screen, and the watch. That last part mattered for us: our watch complications were still running on ClockKit, WidgetKit’s older, watch-only, now-deprecated predecessor. Migrating them over meant retiring a second framework and folding that code into the same toolkit we already used everywhere else</p><h4>How Strava’s widgets are put together</h4><p>Strava’s widgets cannot wait around for the app to hand them fresh numbers. Each one is driven by a timeline provider which is the piece of code that controls a widget’s data and refresh schedule. Each timeline provider stands up its own REST and GraphQL clients and queries Strava’s servers directly whenever the system asks it for a new timeline.</p><p>That’s a deliberate choice. Most people don’t open widgets every hour, but they glance at their home screen dozens of times a day. If a widget could only show whatever the app last pushed to it, your goal ring would be stale most of the time. Making the widget its own client of Strava’s API, rather than a passive mirror of the app, is what keeps it current.</p><p>After a successful fetch, the widget writes its result back into shared storage. That cached copy is kept as the fallback for if a later fetch fails. In such cases, the widget re-renders the last good snapshot instead of showing nothing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*siaByxvzliB4cdV0l9PX4g.png" /><figcaption>Architecture diagram</figcaption></figure><h3>My work</h3><p>Three pieces made up my summer.</p><p><strong>Performance prediction widgets</strong> which are now in internal testing, bring race-time predictions which were previously buried a few taps deep in the app, out onto the home screen.</p><p><strong>Lock screen widgets</strong> let athletes glance at their progress from the lock screen, or launch straight into Strava, without unlocking their phone first.</p><p><strong>Bringing widgets to the watch app</strong> was the most architectural piece of the summer, and the part I’m most proud of. Today, the watch is mostly a recorder. It captures your workout and hands everything off to your phone once you’re done. The team is moving it toward a more independent app, with more capability of its own. My piece of that shift was twofold: firstly expanding goal-tracking directly on the watch, and secondly migrating our old ClockKit complications to WidgetKit.</p><p>The initial plan was to mirror the iOS approach: give each watch widget its own timeline provider that calls Strava’s servers directly, the same pattern described above. That plan ran into a real constraint because watchOS is far stricter than iOS about letting background extensions make independent network requests. Consequently, a widget on the watch can’t reliably act as its own REST client the way an iOS widget can. Mirroring the iOS architecture just wasn’t viable.</p><p>So I re-architected the watch side into two components with a clean split of responsibility:</p><ul><li><strong>The watch app (writer).</strong> Authenticates, refreshes tokens, fetches fresh goal data from Strava’s servers, writes a snapshot to shared storage, and signals the widget that new data is ready.</li><li><strong>The widget (reader).</strong> Reads that snapshot and renders the athlete’s progress with no knowledge of how the data got there, and no network access of its own.</li></ul><p>It’s a small inversion of the iOS model which meant moving from “every widget fetches for itself” to “one trusted writer fetches, many widgets read” but it’s the shape the platform’s constraints actually called for, and it’s the design I proposed and wrote up for the team to build on.</p><h3>What I’m Taking With Me</h3><p>This summer gave me real insight into the consumer product space, working alongside a dynamic, driven team. I learned how to take a fuzzy, hard-to-pin-down goal, something like “make the watch feel less like an accessory,” and distill it into something concrete enough to design against: a shared-storage contract between two components.</p><p>I also came to appreciate what strong documentation actually does. I leaned on past design docs constantly, and wrote several of my own. What I took from that is the value of writing down why a decision was made, not just what it was. The watch architecture went through a hard pivot mid-summer, and it was the doc explaining that reasoning, not just the final design, that let the team pick the work back up without me re-explaining it from scratch.</p><p>And I saw what a genuinely good team culture looks like in practice: something as small as a standing weekly team workout, and a group of people who manage to stay close to the leading edge of a fast-moving field without burning themselves out doing it.</p><p>Thanks to my manager, my mentor, and the whole Achieve team for an incredible summer. I came in wanting to build things that mattered to real athletes, and I’m leaving with a much better sense of how small, thoughtful improvements, a widget, a shortcut, add up to something bigger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kl1okkkWrY3QTiVEWaipAA.png" /><figcaption>Achieve Team Boba</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dabed37298f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/strava-engineering/a-summer-on-the-achieve-team-dabed37298f7">A Summer on the Achieve Team</a> was originally published in <a href="https://medium.com/strava-engineering">strava-engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Mainframes to Models]]></title>
            <link>https://medium.com/@tamakoni/from-mainframes-to-models-add7db7f013a?source=rss-fe2397a00e5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/add7db7f013a</guid>
            <dc:creator><![CDATA[Tanaka Makoni]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 02:12:11 GMT</pubDate>
            <atom:updated>2025-12-02T02:12:11.493Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QcanZSoQhCIBuCtV.jpg" /></figure><p>The rapid evolution of technology keeps educational institutions in a constant state of catch-up. As new tools reshape how people learn, work, and communicate, colleges face the dual responsibility of preparing students for a changing world while also determining the appropriate role that technology should play in the classroom. Yet in the early stages of any technological shift, that role is uncertain, making it difficult for faculty and administrators to craft policies that support innovation without compromising academic integrity or educational values.</p><p>Our visit to the Davidson College Archives offered an illuminating historical parallel. By examining primary sources such as memos, student newspaper articles and administrative reports which documented the arrival of early computers and the internet on campus we gained insight into how earlier generations confronted similar questions. The debates that unfolded at Davidson in the past mirror today’s conversations about generative Artificial Intelligence. Then as now, professors grappled with how to incorporate powerful new tools into coursework, students experimented with both sanctioned and unsanctioned uses, and administrators struggled to define boundaries for ethical and responsible use. This project will be an investigation into how Davidson&#39;s past encounters with transformative technologies can be compared to current attempts to integrate and regulate AI on campus today.</p><h4>Source 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*jZxteNaY_LAwWv0zoymiNg.png" /><figcaption>Memo to College Community after the Introduction of Earliest Computers</figcaption></figure><p>A 1981 memo from Robert P. DeSieno, Director of the Computer Services Center, captures one of Davidson College’s earliest attempts to contend with honor code violations around digital technology. The memo reports an incident in which a student gained unauthorized access to another student’s user-file directory on the campus’s newly installed Prime 750 computer. While the violation itself involved reviewing and transferring files, the memo equates unauthorized digital access with theft. This framing reveals how the introduction of multi-user computing forced the college to rethink its existing Honor Code.</p><p>Before computing, academic institutions relied almost entirely on paper-based systems which used alphabetized folders stored in filing cabinets, documents duplicated by carbon paper or photocopiers, and records physically guarded by administrative staff. These systems were slow but secure, with access requiring a visible breach. The Prime 750 remediated these structures by shifting work into a shared digital environment, promising efficiency, remote access, and centralized storage. At the same time, it introduced new vulnerabilities such as invisible file copying, password misuse, and impersonation which were problems for which the institution had never had to deal with. The “typical” user imagined at the time was a technically fluent student or faculty member in quantitative fields, leaving humanities students and many staff members on the margins of this technological transition. Ultimately, the Prime 750 forced Davidson to redraw the boundaries of academic integrity for a digital age.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6k0HDV8bn4IsxN9lZwgNCQ.png" /><figcaption>Except from current Davidson College Honor Code</figcaption></figure><p>A similar pattern is unfolding today with the rise of generative Artificial Intelligence. AI remediates earlier academic practices such as research, brainstorming, tutoring, drafting, and programming by making them faster and more automated. What once required hours in the library or office hours with a professor can now be simulated in seconds. However, many of these skills are what students have historically developed during the course of their higher education. As can be viewed from the Honor Code except above, the institution’s view on AI is nuanced and still varies depending on individual professor’s preference. While marketed as a “study aid,” generative AI affords students the ability to offload cognitive labor, accelerate research, restructure writing, simulate feedback, or even bypass entire assignments. And unlike with the adoption of the Prime 750, the democratization of technology means that AI tools are accessible to all community members. Davidson is once again navigating the regulation of a transformative technology that challenges existing definitions of integrity, authorship, and learning.</p><h4>Source 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*ijqRwqz70IFWGqIvsXt7Vg.jpeg" /><figcaption>Memo Highlighting the Need for Computers in Liberal Arts</figcaption></figure><p>A 1981 memo from Bob DeSieno to Dean Zimmerman highlights the disadvantages students at liberal arts colleges will soon have if they don’t integrate computers into their curriculum soon. Before computers, learning at liberal arts colleges was through professors directly instructing students and offering personal exchanges. Mr. White is worried that if computers aren’t integrated into the curriculum soon, liberal arts colleges will academically fall behind larger universities. This would ultimately lead students to increasingly turn away from schools like Davidson College, and “thereby diminish the role of liberal education in modern society.” Mr. White believes that, if done correctly, an integration of computers into the curriculum can weave the humanizing aspects of liberal arts education into the use of this technology and help students with their future endeavors after school. Today, AI is having a similar impact on schools around the country. According to professionals surveyed in a SHRM survey, 83% of them believe that AI is foundational to workforce preparedness- those who learn to work with AI will have an advantage in the future.</p><p>The goal of this transition was to equip students and faculty with the use of computers and the quantitative thought that they accompany. What had always worked for liberal arts colleges prior was their emphasis on personal exchanges between faculty and students. In the past, that technical human education more than compensated for aging equipment. The result of this new addition of computers would inevitably decrease the emphasis and priority on this kind of learning. The integration of AI into students’ lives is having a similar effect. Now, before reaching out to teachers, students first turn to this technology to save time, improve the quality of their work, and increase or sharpen their understanding of concepts. The roles of teachers continue to diminish as AI continues to assist students and their academic needs.</p><p>The typical user was faculty and students who wanted to pursue careers in scientific fields and went on to larger universities to continue their research. A large part of this paper pushes for people to develop quantitative thought which excludes lots of humanitarian fields. Today, AI is seen benefiting those in knowledge or creativity based fields the most.</p><p>Early computing infrastructure was controlled by administrators. However, today, administration at schools struggle to keep up with evolving AI. While Davidson staff enforces rules like not allowing any confidential data to be used in any AI tool without explicit permission from T&amp;I Information Security, it is difficult to enforce and regulate these rules when students have so much freedom and access to AI. Davidson is continuously trying to adapt to ensure their goals align with evolving AI.</p><h4>Source 3</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*u7PZA3a4lvsPxf_GiWcNCA.jpeg" /></figure><p>The Newsletter of the Davidson College Computer Center was first released on September 14, 1981, and was used to document the installation of new computing technology on campus. Prior to this update of machinery, computers didn’t have interactive computing. With these new system, users could insert a prompt using a keyboard and get quick responses in the administrative offices which ended the dependence of IBM cards for the entry of data into computers. This was believed to make the use of computers more accessible for a greater number of students who didn’t have this skill. This explosion of accessibility of computers is similar to AI. There are numerous free platforms making it easy for anyone to use, and giving students new opportunities to learn more quickly.</p><p>Similarly, the intended use of these new super mini computers was to give more opportunities to students while also allowing administrative offices to maintain direct control of their files. It was valuable to research and learning. Some unintended consequences were the increase of collaboration. This new printer that printed hard copies at a faster speed than before allowed for more people to create physical copies of their work and exchange or share their ideas with other people. AI continues to foster this collaborative environment. The AI Innovation Initiative hosts frequent jam sessions, training opportunities, and other fun ways to engage with classmates all around the campus.</p><p>The vast majority of the Prime 750 users were students specifically conducting research in scientific fields. Equipped with all programming languages and the Statistical Package for the Social Sciences, it was intended to be a valuable resource for research and courses at Davidson College. Now, AI can be used but not limited to writing and summarizing documents, analyzing data, developing websites and presentations and writing code. Students in almost every field can use AI to assist them in their work.</p><p>The Information System maintained a system where the administration would have more power than students as they had access to all the files and any responses to inputs to the main Prime 750 went to administrative offices. While it is difficult to monitor how every student uses AI, the trust and integrity that underlie the Honor Code extend to how AI is expected to be used on campus.</p><h4>Source 4</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*q2zYpNmR-OVp2WS42EFlrQ.jpeg" /><figcaption>Memo Announcing the Appointment of new Director of Computer Services</figcaption></figure><p>A 1980 presidential memo announcing the appointment of Professor Robert P. DeSieno as Davidson’s Director of Computer Services provides a critical snapshot of how the college positioned itself at the beginning of the digital era. The memo frames the appointment as a “key step in a substantial broadening of our computer capability,” emphasizing that expanded access to computing would soon be one of the distinguishing features of a competitive liberal arts institution. This reflects an early institutional recognition that computing was not simply a technical tool but an academic necessity one that required proper curricular integration. By appointing a chemist with demonstrated expertise in computing, the college signaled that technological fluency was no longer confined to just computer science but rather it was becoming a core interdisciplinary skill. The memo also highlights a shift from viewing computing as an optional resource to seeing it as core infrastructure for student success. Offering students “a full range of computer services” was framed as an academic differentiator, underscoring the belief that technological access would shape the future of learning. This multi-disciplinary approach and broad scope of learning is right at the heart of liberal arts education. Yet this transition also created new responsibilities such as developing policy, training faculty, and ensuring campus wide accessibility for all students.</p><p>A similar pattern is visible today with the rise of generative Artificial Intelligence. Currently Davidson continues to establish dedicated administrative structures to guide the integration of the new technology. There are AI task forces consisting of both students and faculty, student panels and campus wide push for developing clearer guidelines to regulate AI use. Some of these bodies include the Honor Council’s AI team or T&amp;I’s student AI team. Additionally, there are considerations of bringing new faculty with particular expertise in AI into the computer science department to better prepare students to work alongside AI tools. Similarly AI is being framed as a competitive necessity for the college. It is an asset that can enhance teaching, expand research opportunities, and prepare students for an evolving workforce. At the same time, the technology raises new challenges around academic integrity, and faculty preparedness, echoing the questions that accompanied the first wave of computing in 1980. Further, there is the recurring theme surrounding technology and the liberal arts, that even in non-technology related fields, a liberal arts education is supposed to equip students with technical competence. Across both moments, Davidson’s actions reflect the same underlying impulse which is that major technological shifts require intentional leadership, institutional investment, and a rethinking of what it means to offer a forward looking liberal arts education.</p><h4>Conclusion</h4><p>The impact of early computer adoption strongly mirrors the swift influence of AI on college campuses around the nation today. Just as computers introduced new forms of efficiency, inquiry, and collaboration, AI now serves as a powerful academic tool that can enhance student learning and potentially create disparities between those who use it and those who do not. At Davidson, the initial arrival of computers was tightly managed by administrators, who strictly controlled early usage policies. As the technology continued to evolve, those policies had to be constantly reconsidered. Similarly, the growing presence of AI will require updated guidelines that balance innovation with academic integrity, ensuring that students, especially within liberal arts institutions, can still benefit from these tools while maintaining the core values of critical thinking and independent learning. Ultimately, studying how Davidson College navigated the immersion of computers on their campus highlights that technological change is not new; what matters is how colleges decide to guide students through this transition.</p><h4>Bibliography</h4><p>“Artificial Intelligence.” <em>Davidson</em>, <a href="http://www.davidson.edu/ai.">www.davidson.edu/ai.</a> Accessed 1 Dec. 2025.</p><p>DeSieno, R. Memo to Faculty, Students, and Staff. 11 December 1981. RG 15.03. Computer Services. Memorandums, Announcements. Davidson College Archives, Davidson College, NC.</p><p>DeSieno, R. Critique of the Essay, “The New Liberal Arts”. 30 March 1981. RG 02.15. President Spencer Box 23. Davidson College Archives, Davidson College, NC.</p><p>Legatt, Dr. Aviva. “90% of College Students Use AI: Higher Ed Needs AI Fluency Support Now.” <em>Forbes</em>, Forbes Magazine, 18 Sept. 2025, <a href="http://www.forbes.com/sites/avivalegatt/2025/09/18/90-of-college-students-use-ai-higher-ed-needs-ai-fluency-support-now/">www.forbes.com/sites/avivalegatt/2025/09/18/90-of-college-students-use-ai-higher-ed-needs-ai-fluency-support-now/</a>.</p><p>Robertson, Craig. “The Filing Cabinet.” Places Journal, May 1, 2021. <a href="https://placesjournal.org/article/the-filing-cabinet-and-20th-century-information-infrastructure/">https://placesjournal.org/article/the-filing-cabinet-and-20th-century-information-infrastructure/</a>.</p><p>Samuel R Spencer,. Memo to Faculty, Students, and Staff. 11 December 1981. RG 15.03. Computer Services. Memorandums, Announcements. Davidson College Archives, Davidson College, NC.</p><p>The Newsletter of The Davidson College Computer Center Vol. 1 №1. 14 September 1981. RG 3/10.2. Informational Technology Services. Davidson College, NC.</p><p>“Prime 750.” Chilton. Accessed December 1, 2025. <a href="https://www.chilton-computing.org.uk/acd/icf/mums/p020.htm">https://www.chilton-computing.org.uk/acd/icf/mums/p020.htm</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=add7db7f013a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing For Accessibility]]></title>
            <link>https://medium.com/@tamakoni/designing-for-accessibility-829f2a426d93?source=rss-fe2397a00e5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/829f2a426d93</guid>
            <dc:creator><![CDATA[Tanaka Makoni]]></dc:creator>
            <pubDate>Sat, 18 Oct 2025 22:10:58 GMT</pubDate>
            <atom:updated>2025-10-18T22:10:58.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*P04kIQdSt54DUfJZ.jpg" /><figcaption>Image of Davidson College Campus</figcaption></figure><p>Before this project, I had gone through most of my days oblivious to questions of accessibility and the amount of thought that must go into correctly navigating Davidson’s campus. If any thought had gone into it, I would have assumed the campus was easily accessible. Between all the ramps and automatic doors surely the campus was easily accessible.</p><p>However, after spending 24 hours navigating Davidson College exclusively through handicap-accessible pathways, I developed a far deeper appreciation for the challenges faced by those with accessibility needs. This experience taught me that accessibility is not just about the <em>presence</em> of ramps or elevators, it’s about <em>how well those features are integrated</em> into the daily movement of the campus community.</p><h3>Overview of my 24 hours</h3><p>For this challenge, I committed to traveling for a full day without using stairs, curbs, or unpaved paths. That meant no cutting across grass, no hopping onto curbs, and no taking shortcuts. I could only use paved paths, ramps, and automatic doors.</p><p>I live in Richardson Hall, a centrally located residential building on campus. That made navigation somewhat easier, but it also forced me to be more deliberate in planning my routes. Even small changes in path choice required forethought and time. While the detours didn’t drastically increase my walking time, they made me acutely aware of the mental effort required to move around in an accessible way.</p><h3>Watson Academic Building</h3><p>I started my day at 7:30a.m. with breakfast before I headed to class. I made a short trip to commons using a slightly unusual path that warps around the outside of the building before walking over to Watson for my first class. Watson is one of the major academic buildings on campus and is one of the more accessible academic buildings at Davidson because both of its main entry ways are automatic, it has an elevator and is easily navigable.</p><p>It features:</p><ul><li>A ramp at the main entrance, seamlessly integrated with the building’s design</li><li>A spacious elevator that services all floors</li><li>Electronic doors that respond quickly to button presses</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1in4QqHNHVlPGjOVq7rDg.png" /><figcaption>Images of Accessible features from my morning</figcaption></figure><h3>Nummit</h3><p>After class I headed over to Summit Coffee Outpost to grab coffee. This is a popular spot for students to hang out, work and grab coffee from on campus. However, the front door is inaccessible because of the stairs that lead up to it forcing students to enter through the back door. The back entrance presents its own set of issues:</p><ul><li>There is no fully paved path leading directly to the back.</li><li>The area is sometimes blocked by trash bins as it is a service route.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xv4umF0KXUU_J0PNdpS0hw.png" /><figcaption>Images Showing Poor Accessibility Design</figcaption></figure><h3>Lula Bells</h3><p>My next stop was Lula Bell’s Resource Center, where I volunteer regularly. This location offered an interesting thought case because, on paper, it’s a model of good accessibility. The building has a <strong>r</strong>amp leading up to the entrance, a wide automatic door, and open interior spacing that allows easy movement for wheelchairs or mobility aids. Inside, the aisles are arranged to accommodate a turning radius for wheelchairs, and display tables are set at a reachable height.</p><p>However, I quickly realized that accessibility isn’t just about design but also about <em>maintenance and daily use</em>. When I arrived for my volunteer shift, a golf cart had been parked directly in the handicap parking spot, partially blocking the entrance. What was designed to be an accessible and welcoming front quickly became an obstacle.</p><p>This moment perfectly captured how human behavior can undermine accessible design. Even the best-designed environments can lose their inclusivity if accessibility features are misused or obstructed. It reminded me that accessibility isn’t a one-time infrastructure project but an ongoing commitment that requires social awareness and community respect</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*ALOLnKRKL94EMyVpNnXj7w.jpeg" /><figcaption>Photo of a golf cart blocking the handicap parking space</figcaption></figure><h3>Chick-fil-A</h3><p>For dinner, I visited the Chick-fil-A. With this being the newest addition to campus I was intrigued to see if accessibility requirements had been considered. Some of the measures put into place include:</p><ul><li>A clearly marked ramp leading directly to the main doors</li><li>Automatic door buttons on both entrances</li><li>Wide pathways with minimal obstructions</li></ul><p>These features made the space itself accessible but getting across campus required extra planning. Some of the sidewalks leading to the complex lack curb cuts, and the nearest crosswalks are spaced far apart, forcing detours for those relying on mobility devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*svSSquqQeIdamZL1WmLIEA.jpeg" /><figcaption>Image of ramp at the new Chick-fil-A on campus</figcaption></figure><h3>Cannon Residence Hall</h3><p>Perhaps the most limitation I observed on campus lies in Cannon Residence Hall. The building lacks an elevator entirely, as do Little Hall and Sentelle Hall, two other residence halls along dorm row. This means that any student with a mobility impairment would be unable to live on the upper floors of these buildings.</p><p>This inconsistency in accessibility has broader implications for campus life. It limits housing options for students with disabilities and restricts their ability to fully participate in the social and communal aspects of residence life. Even temporary injuries such as a broken leg or sprained ankle would drastically affect a student’s ability to live comfortably or independently in these halls. Which, for an institution with a significant athlete population is a cause for concern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ad3i4gY6pznMVvp3mPZASQ.jpeg" /><figcaption>Image from Cannon Residence Hall</figcaption></figure><h3>Mapping</h3><p>After spending the day navigating only accessible routes and documenting my experiences through photos and notes, I turned to the task of visualizing these findings. I wanted my map to not just show <em>where</em> accessibility features existed, but also to communicate <em>how well</em> those features worked together to create a truly inclusive environment.</p><p><strong>Version 1</strong></p><p>To begin, I opened Google My Maps and imported an empty outline of the Davidson College campus. This blank map became my foundation. I then pinned the key buildings I had visited throughout the day. It includes Richardson Hall, Watson, the Visual Arts Center, Nummit, Chick-fil-A, Lula Bell’s, and Cannon Residence Hall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LWk71OaWwgwF82ReMMJJA.png" /><figcaption>Initial Map V ersion</figcaption></figure><p><strong>Version 2</strong></p><p>Building on this first draft, I began to add color coding and paths to navigate across campus. Each building pin was color-coded based on its accessibility rating from my field notes. I also traced the routes I took throughout the day to show how accessible they were</p><p>The map uses the following visual language:</p><ul><li>Green location icons for accessible buildings</li><li>Red location icons for inaccessible a buildings</li><li>Green lines accessible paths</li><li>Red lines inaccessible paths</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QloLJhUlSv4eswwedq5cw.png" /><figcaption>Second Map Version</figcaption></figure><p><strong>Version 3</strong></p><p>Realizing this oversight, I decided to rework my color palette using blue and black, which provide higher contrast and are more readable across forms of color vision deficiency. In the end the map used the following visual language:</p><ul><li>Blue location icons for accessible buildings</li><li>Black location icons for inaccessible a buildings</li><li>Blue lines accessible paths</li><li>Black lines inaccessible paths</li></ul><p>Lastly I added icons to help increase the interpretability of the map. The icons showed areas that were only accessible using stairs and that had automated doors</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSrhftxY-9pHS0U_MzfTLA.png" /><figcaption>Final Map Version</figcaption></figure><h3>Conclusion</h3><p>Spending a day navigating the campus through accessible routes forced me to think differently about design. Accessibility is not simply about compliance or checking boxes, it’s about empathy, anticipation, and inclusion. The idea of accessible design is that it seamlessly integrates, so that it doesn’t feel like an accommodation but like the natural state of the environment. Yet, throughout much of my day, accessible features, while available, felt like an afterthought. As a consequence much of my mental load was dedicated towards figuring optimal pathways rather than simply following the natural flow. The need for constant calculation and consideration is an indication of poor design from an accessibility standpoint.</p><h4>Key Takeaways</h4><ul><li><strong>Strengths:</strong> Davidson has made significant progress in academic spaces like Watson and the Visual Arts Center, where accessibility feels natural and convenient.</li><li><strong>Weaknesses:</strong> Social spaces and some residential areas remain behind and inaccessible to part of the student body.</li><li><strong>Opportunities:</strong> Small design updates like adding curb cuts, and clearer signage could dramatically improve inclusivity with minimal structural changes.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=829f2a426d93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping a Health Insurance Billing Support App]]></title>
            <link>https://medium.com/@tamakoni/prototyping-a-health-insurance-billing-support-app-8e86e889a64f?source=rss-fe2397a00e5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e86e889a64f</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Tanaka Makoni]]></dc:creator>
            <pubDate>Fri, 19 Sep 2025 02:47:27 GMT</pubDate>
            <atom:updated>2025-09-19T02:47:27.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*YICblGIK9bp6XZL6.jpg" /><figcaption>Medical Billing Graphic</figcaption></figure><p>I previously wrote about needfinding in the healthcare billing space. Continuing that research, I aim to implement the feedback I received in the needfinding process to create a paper prototype of a medical billing support app. Medical billing in the U.S. is rarely simple. Patients face jargon-filled statements, duplicate charges, and surprise costs that create confusion and stress. Even insured individuals struggle to trust what they owe. Through needfinding interviews, I discovered that while these challenges differ across life stages, they share common roots in fragmentation, complexity, and poor communication.</p><h3>Defining the problem</h3><h3>The User</h3><p>Understanding the complexity of medical billing required hearing from people at different stages of life and with varying levels of interaction with the U.S. healthcare system. To do this, I conducted three targeted interviews: a young adult international student, a retired older adult managing a chronic illness, and a Student Health Center staff member who handles billing and insurance issues daily. Each participant was intentionally selected to highlight both the lived experiences of patients and the systemic challenges seen from the administrative side.</p><h3>POV Table</h3><p>Based off those conversations during the initial Needfinding stage, I have here are the POV (Point of View) tables to sum their experiences:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JSRXVkQTJExMRYT-NAD2CQ.png" /><figcaption>POV Table from Interview 1</figcaption></figure><p>The <strong>international student</strong> represented the perspective of someone navigating U.S. healthcare for the first time. Her confusion over what her student health plan covered, combined with shock at unexpected bills underscores the financial vulnerability of patients without established family or community safety nets. Her distrust of the system, heightened by receiving clearer care abroad at a fraction of the cost, makes a strong case for an app that can translate jargon heavy bills into plain language and highlight coverage gaps before they lead to financial crises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZbQaR1ksTUviAoV4jJUkA.png" /><figcaption>POV Table from Interview 2</figcaption></figure><p>The <strong>retired older adult with diabetes</strong> offered insights from the perspective of long-term system engagement. Despite decades of experience with insurance, he still faced late claims, coverage instability (such as annual changes in insulin coverage), and the exhausting burden of long hold times when seeking clarification. At times, he even paid questionable bills just to avoid the stress of disputes. His experience illustrates the need for features like coverage stability alerts, a deductible/copay tracker, and analytics that make year on year spending and coverage changes more predictable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVNLke46kRpmMW4ySw_z2g.png" /><figcaption>POV Table for Interview 3</figcaption></figure><p>Finally, the <strong>Student Health Center staff member</strong> acted as an “extreme user” on the administrative side. They see the billing system’s flaws magnified through repeated daily interactions with confused students. Their perspective highlighted systemic issues, such as students mistaking EOBs for bills and being penalized by small coding differences beyond their control. Their experience confirmed the need for tools that reduce panic and misunderstanding, such as an automatic bill/EOB explainer, a coding translator, and an educational glossary to improve baseline literacy.</p><p>After going through this process, these are the insights are arrived at to help guide my problem solving approach:</p><ul><li><strong>Bills and explanations of benefits are confusing.</strong> Patients often misinterpret EOBs as bills, leading to unnecessary panic.</li><li><strong>Surprise charges erode trust.</strong> Participants felt blindsided when coding differences or denials led to unexpected bills.</li><li><strong>Chronic care patients face instability.</strong> Frequent changes in what drugs or services are covered create stress and financial strain.</li><li><strong>Administrative inefficiencies lead to resignation.</strong> Some patients simply pay questionable bills to avoid long, exhausting disputes.</li><li><strong>Students lack baseline literacy.</strong> Many only learn about insurance when something goes wrong, leaving staff to “translate” on their behalf.</li></ul><h3>How Might We (HMW) Questions</h3><p>The insights drawn from my interviews directly informed the framing of several How Might We (HMW) questions. Each one is rooted in a specific participant’s experience but also reflects broader systemic problems in medical billing. These questions helped me as I worked to transform participant frustrations into design opportunities. Some questions I came up with are:</p><ul><li>How might we help patients understand their bills and EOBs at a glance?</li><li>How might we prevent surprise charges by improving transparency before care is delivered?</li><li>How might we reduce the emotional toll of dealing with insurance disputes?</li><li>How might we give chronic care patients consistency in coverage and billing?</li><li>How might we empower students and first-time users to build literacy without being overwhelmed?</li></ul><h3>Ideation</h3><p>Based on these insights, I identified several potential features that could be included in my final solution</p><ul><li><strong>Plain-Language Bill Explainer</strong>: Upload a bill or EOB and receive a simplified breakdown of what each charge means.</li><li><strong>Real-Time Coverage Checker</strong>: Before a procedure or prescription, the app verifies coverage and out-of-pocket costs.</li><li><strong>Coding Translator</strong>: Shows how small differences in billing codes affect charges, helping patients contest errors.</li><li><strong>Coverage Stability Alerts</strong>: Notifies chronic care patients when formulary or coverage rules change, reducing surprises.</li><li><strong>Interactive Learning Module</strong>: A student focused feature that gamifies insurance literacy with simple scenarios. It gives them access to a glossary of insurance and billing terms with range of articles they can read through</li></ul><h4>Potential Solution</h4><p>By bringing together these perspectives, the solution I arrived at was a consumer facing mobile app that acts as a personal medical billing support tool. The app allows users to scan and digitize medical bills, explanations of benefits (EOBs), and insurance paperwork. Using AI and natural language processing, it interprets these documents and presents the information in plain language so patients clearly understand what is covered, what they owe, and why. Beyond interpretation, the app centralizes all bills, payments, and insurance tracking into one simple dashboard, creating a single, reliable space to manage healthcare finances. To further empower users, it also provides education and literacy tools that help patients navigate the system more confidently and advocate for themselves.</p><p>The app’s key features make this possible. A smart document scanner and interpreter lets users upload bills, EOBs, or insurance letters, which are then broken down into clear, digestible explanations. A centralized bill and payment tracker ensures that all current and past bills are stored in one place, with progress tracking for ongoing payments and reminders to prevent late fees. A dedicated deductible and copay dashboard syncs with insurance information (or allows for manual entry) to track how much of the deductible has been met, upcoming copays, and annual out-of-pocket totals. An analytics and insights section provides year on year visualizations of healthcare spending, breaks costs down by category such as doctor visits, prescriptions, or diagnostics, and alerts users to unusual charges or spending spikes. Finally, an education and resources section includes a glossary of billing and medical terms, quick guides to common issues like deductibles and copays, and curated articles to help users navigate disputes, appeals, and coverage changes.</p><h4><strong>Competitors</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X_aRFvkYKJYmEaU7" /><figcaption>Logo of Playgroung — An Existing Medical Billing App</figcaption></figure><p>While the medical billing support space already has other players, there are significant gaps that a more comprehensive solution could address. Apps like PayGround or MedPayGenie focus on consolidating bills from different providers and enabling quick, flexible payments. However, they fall short when it comes to interpretation, analytics and in helping users understand the details of their bills or insurance paperwork. Further, most solutions struggle with providing transparency. Patients still struggle to understand <em>why</em> they owe what they owe and almost none provide robust educational tools to increase literacy around insurance and billing practices. Proactive alerts and cross-provider integration are also rare, leaving patients with fragmented experiences.</p><h3>Prototyping</h3><p>I began the prototyping process with a series of rough sketches. Sketches are considered a low fidelity prototype whose goal is to quickly test an idea and evaluate how it can improve. Low fidelity sketches lay the groundwork for cleaner, well thought out paper prototypes.</p><p>My initial sketches were of the homepage. I began here because it is the screen users will see first and will anchor the rest of their experience. I made a series of 6 homepages, each experimenting with how to display core information such as balances, bills, and alerts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*yzRmpI7nlDsf_FCDsalRbg.jpeg" /><figcaption>Home Tab Prototypes</figcaption></figure><p>The first sketch emphasized quick access to current balance and latest bills, with shortcuts at the bottom for rapid navigation. The second prototype organized the homepage as a dashboard, prioritizing balance and recent transactions in larger blocks. In the later designs, I added more nuanced features such as alerts for due bills, summaries of payments, and visual cues for bill status. I realized that one central functionality that was not emphasized enough in most of my homepage variations was the scan/upload button for documents. Through these iterations I was able to compare a minimalist dashboard approach with more detail-rich layouts, eventually moving toward a design that balances clarity with functionality.</p><p>The next prototype I looked to design was my Analytics tab. The idea for this page was having an area where users can see long term trends in their healthcare spending and detailed breakdown of each transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*niyFFQ1eFsD7LafyoWXxsg.jpeg" /><figcaption>Analytics Tab Prototype</figcaption></figure><p>The first design featured a high-level overview with charts showing paid, unpaid, and overdue bills, alongside a monthly spending line graph. The second sketch tested a more statistics driven layout, with bar graphs and transaction summaries. To dig deeper, I also designed an analytics detail view, where users can tap into an invoice for a breakdown of items, quantities, and costs, with reminders attached to due dates. Through this sketching process I was able to think through how much information should be visible at a glance versus what should be revealed on deeper pages.</p><p>The last prototype was for the education tab which will serve as the knowledge hub for users as they develop a deeper understanding of billing and insurance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*TCuJmYDqZIkRh9VXeR1sTg.jpeg" /><figcaption>Education Tab Prototype</figcaption></figure><p>I played around with grid layout and list based approaches to presenting information. In particular the 3rd sketch combined these elements. Another major thing which I hoped to make clearer with the 3rd sketch was a personalizable approach to saving articles which will be pinned at the top of the page. I think this would be so useful as users of different expertise levels can all make use of the app and personalize it to the specific information they need.</p><h3>Feedback</h3><p>User testing is a central step in refining any project design. And while I could not get my actual users to test the design, I got feedback from some classmates. Despite the obvious limitations in working with my classmates, by walking them through my homepage, analytics, and education sketches, I was able to collect feedback on what elements worked well and what needed to change. Their insights shaped how I revised the prototypes into their more finalized versions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*6W5Bird_erVSZ0bjStnyWg.jpeg" /><figcaption>Feedback Session with Maria</figcaption></figure><h4><strong>Homepage Prototypes</strong></h4><p>From my first interview, Maria appreciated the “Latest Bills” section but suggested using a vertical stacking layout in design #1 to better accommodate a longer list of bills. This idea carried forward into the final design. In contrast, the second prototype received criticism for being cluttered and overwhelming, particularly with the dashboard-style layout. Users also felt that tabs for homepage navigation as seen in design #3 were unnecessary, which led me to simplify the structure. Across all iterations, users liked the “Quick Actions” feature. Based on this feedback, the final homepage design uses a vertical bill layout, retains Quick Actions with icon-based navigation, and introduces a bottom navigation bar for persistent, intuitive access.</p><h4><strong>Analytics Prototypes</strong></h4><p>The analytics page was consistently seen as a strong idea. In design #2, the bar graphs were praised for their clarity, and Mali noted that double bars gave a stronger visual indication of progress than the line graph. However, others suggested that a line graph could also be useful for showing change over time. General feedback emphasized the importance of seeing details about deductibles, copays, and coinsurance.</p><h4><strong>Education Prototypes</strong></h4><p>Feedback on the education section was decisive. The first and third designs were not well received, primarily due to poor use of space. Design #2, stood out for its glossary of terms and well organized categories. Users valued the ability to pin items and filter information, as well as the inclusion of a search bar for quick access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*Ayz8b5vUNw8vtejDY8EL5w.jpeg" /><figcaption>Feedback Session with Mali</figcaption></figure><h4><strong>Application of Feedback</strong></h4><p>Across all three sections, user input highlighted the importance of clarity, reduced clutter, and meaningful navigation. Their feedback was used to refine the homepage to emphasize quick actions and transparency, strengthen the analytics page with intuitive graphs and detailed breakdowns, and streamline the education page to prioritize search, glossary tools, and saved resources. The result is a set of prototypes that better align with user needs, reducing confusion and improving usability.</p><h3><strong>Final Prototypes</strong></h3><p>After several rounds of sketching, feedback, and revision, I arrived at a set of final paper prototypes that integrate the most effective elements from earlier designs while addressing the key concerns raised by users. These prototypes represent a more polished vision of the app and reflect a balance between clarity, functionality, and ease of use. Together, they work to reflect the project’s core goals which are:</p><ul><li>to reduce confusion,</li><li>improve transparency, and</li><li>give patients practical tools to navigate the billing process with confidence.</li></ul><p>The homepage in particular underwent the most significant revisions based on user input. On the Homepage, I emphasized a clean vertical stacking layout for bills, retained the Quick Actions feature, and introduced a persistent bottom navigation bar to simplify movement between sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*PmLAmVKglaD6LVQqMu-9Fw.jpeg" /><figcaption>Final Home Tab Prototype</figcaption></figure><p>The final design for the Analytics Page incorporates all of the insights from feedback. It keeps the bar graph as the centerpiece, adds clear year on year comparisons, and adds a table section so users can track what has been paid versus what was still owed. The page focuses on clear year on year bar graphs and adds details for deductibles, copays, and coinsurance, making costs easier to interpret at a glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*oIJfQmoyWio6SjUQAZmO8Q.jpeg" /><figcaption>Final Analytics Tab Prototype</figcaption></figure><p>Finally, using insights from the interviews the Education tab featured a clean search bar at the top, a category section for filtering, and a “Saved” section for pinned items. The layout was simplified to reduce visual clutter and improve readability. The tab organizes resources through a search bar, glossary, and customizable categories, ensuring users can quickly find and save the information most relevant to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*HrWaZ-97EhmIQ4QKHQyqEA.jpeg" /><figcaption>Final Education Tab Prototype</figcaption></figure><h3>Evaluation Plan</h3><p>As previously pointed out, there are many limitations to having my peers give me design feedback. If time and resources were not a constraint, I would design a more extensive multi stage evaluation process to test whether the app truly simplifies medical billing, improves users’ understanding of insurance, and empowers them to manage their healthcare costs. My plan would combine usability testing, comparisons between competitors, and expert feedback to ensure both the design and the outcomes are rigorously assessed.</p><p>The first step would involve implementing a user centered method for evaluating designs. Through a series of structured testing sessions, participants would be given real medical bills and insurance documents to scan and insurance. I would track how quickly and accurately they navigate to key information, such as “how much do I owe?” or “how close am I to meeting my deductible?” A diverse group of participants, including people with varying levels of healthcare literacy would be selected. Surveys and personal feedback sessions would be conducted to provide insight into whether the plain language interpretations are clear and helpful.</p><p>These sessions would also include users of competitor sites so that a direct comparison can be drawn to see what areas are our unique selling points versus what could potentially be improved. If conducted over a long period, a control group of participants who do not use the app could be compared to people who have adopted the app to directly measure whether the app significantly outperforms existing approaches.</p><p>Additionally, analysis of in-app data to identify user patterns such as which features are most used, where users drop off, and how often they engage with the different resources. It would also be important. Further getting healthcare billing experts and insurance professionals to ensure the app’s document interpretations, ensuring the information presented to users is correct, consistent, and aligned with industry standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GqehUsp1jcRb3EZs.jpeg" /></figure><h3>Conclusion</h3><p>This project set out to address the confusion and stress patients face with medical billing in the U.S. Through interviews and iterative prototyping, I hoped to increase clarity in billing, provide greater transparency around costs, and build insurance literacy. Through brainstorming, prototyping and user feedback I was able to develop a Minimum Viable Product (MVP) for the homepage, analytics, and education sections. While limited in scope, the process demonstrated how thoughtful design can make complex systems more understandable. With further testing and validation, this app has the potential to not only simplify billing but also empower patients to manage their healthcare costs with greater confidence and ease.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e86e889a64f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Needfinding: Health Insurance & Medical Billing]]></title>
            <link>https://medium.com/@tamakoni/needfinding-health-insurance-medical-billing-3f3d6c23463c?source=rss-fe2397a00e5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f3d6c23463c</guid>
            <category><![CDATA[health-insurance]]></category>
            <category><![CDATA[medical-billing]]></category>
            <category><![CDATA[needfinding]]></category>
            <category><![CDATA[medical]]></category>
            <dc:creator><![CDATA[Tanaka Makoni]]></dc:creator>
            <pubDate>Fri, 19 Sep 2025 01:44:31 GMT</pubDate>
            <atom:updated>2025-09-19T01:44:31.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vqv09q333GLvmV8u.png" /><figcaption>Health Insurance Graphic</figcaption></figure><p><strong>Introduction</strong></p><p>Medical billing in the U.S. is rarely simple. Patients often face jargon filled statements, duplicate charges, or surprise costs that create confusion and stress. Even insured individuals struggle to trust what they owe. These challenges cut across the system so whether you are a student navigating insurance for the first time, a working adult managing high deductibles, or an older individual coordinating Medicare, they share common roots in fragmentation, complexity, and poor communication. Through interviews with people from varied backgrounds, this project explores how patients experience billing with the goal of discovering shared needs and identifying opportunities to make the process clearer, less financially burdensome, and more humane.</p><h3><strong>Needfinding Methodology</strong></h3><p><strong>Participants</strong></p><p>When considering who to interview, I prioritized including extreme users of the healthcare system. For example, administrative staff who work daily with insurance claims experience the system at its most complex. Their perspective helps reveal pain points that ordinary patients may also encounter, but less frequently. By learning from their concentrated experiences, I can better understand breakdowns that ripple through the system as a whole.</p><p>I also considered age and life stage as a key factor. A young adult managing health insurance independently for the first time often feels confused by premiums, deductibles, and surprise bills, while an older adult on Medicare may face challenges reconciling multiple statements or coordinating supplemental coverage. Including participants from different life stages helps surface how billing challenges evolve as people’s healthcare needs and coverage types change.</p><p>Finally, I sought diversity in roles and health contexts. Patients who primarily use preventive care have very different billing experiences than those who face emergencies, chronic conditions, or complex treatments. Balancing patient voices with the perspective of administrative staff allowed me to see both sides of the process. Both how bills and insurance claims are generated, and how they are experienced by those asked to pay them.</p><p><strong>Interview Questions</strong></p><p>My approach to forming interview questions was informed by the principle outlined by Amy J. Ko on needfinding interview best practices. The structure begins with rapport-building questions to get to know them.</p><ul><li>Tell me about yourself? Where are you from, what do you do, how old are you?</li></ul><p>Having eased participants into the conversation and gathered some contextual information, I was ready to probe deeper into the participant’s relationship with insurance. This question evoked stories or allowed participants to begin exploring their emotions. Further, I asked participants to recall their most recent medical bill or explanation of benefits, which encouraged concrete storytelling rather than abstract opinions, helping surface real, specific details of the billing experience.</p><p>The next section focuses on specifics about the interviewees general responses to billing information, general feelings and brainstorming possible solutions helping build a holistic picture of the patient experience. A struggle was ensuring I was not asking leading the conversation and not guiding the interviewee down a single path.</p><ul><li>Can you walk me through what usually happens from the moment you receive a medical bill to how you act on it?</li><li>What feelings typically come up when you receive bills or insurance correspondence?</li><li>If you could redesign the billing or insurance process, what would your ideal experience look like from receiving care to paying the bill?</li></ul><h3><strong>Interview Results</strong></h3><p><strong>Participant 1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*wtM4UmOXW3CRQc-ewEqxJQ.png" /><figcaption>Interview conducted over coffe at Nummit</figcaption></figure><p>Participant 1 is a 22-year-old international student at Davidson College who has had frequent interactions with the U.S. healthcare system during her time on campus. She identifies as female and as someone new to American insurance and billing practices, she provides the perspective of a user still adapting to an unfamiliar and often overwhelming system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3gX6_f4u-26RWt5YtLx6Q.png" /><figcaption>Participant 1 Empathy Map</figcaption></figure><p>Her experiences reveal confusion and frustration at multiple levels. She is unsure what her student health plan actually covers and finds hospital billing practices unclear and inconsistent. She has faced large, unexpected charges with her most recent bill approximately totalling $12000 at the beginning of the summer, for what she assumed should be fully covered ER visits. She contrasts this experience with the type of service she has received later that summer while abroad. After participant 1’s issue resurfaced while she was abroad, for a tenth of the price, participant 1 received better quality service, clearer communication and the correct diagnosis. Yes, so even after her $12000 hospital visit, it took leaving the country to get an accurate diagnosis and treatment. This experience only heightened her distrust of the system. To this day she is still fighting the American hospital to get access to test results so she can have an up to date health record. For her, the lack of transparency made it feel like the system was not only broken, but predatory especially for people without family safety nets. More generally, she commented on small differences in the time doctors spent with her in the two countries and the level of support she felt through the process. Her account illustrates how billing inconsistencies erode trust in the system and create barriers to effective care. From her account, I arrived at the following insights:</p><p><strong>Insight #1:</strong> Patients need clear, itemized bills that explain exactly what each charge is for, in plain language.<br><strong>Insight #2:</strong> Hospitals and insurers should prioritize informed consent by explaining procedures and test results before billing for them.</p><p><strong>Participant 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7qNIb-vW_Femt0kjioRdkQ.png" /><figcaption>Zoom interview with Participant 1</figcaption></figure><p>This participant is a retired older adult living with diabetes who relies on Medicare along with supplemental insurance. After decades of managing his condition, he has developed a deep familiarity with the system but still finds it frustrating and unnecessarily complex. His worst ever experience was when a claim was submitted late, and as a result part of the charges were initially denied by Medicare, leaving him confused, especially since he had already met his deductible for the year. His immediate response was to call the billing office for clarification, but long hold times and poor communication left him feeling ignored. In the end, he paid the bill to avoid the stress of fighting with insurers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SvSaOyD0g0VDwxxIcLwyoQ.png" /><figcaption>Participant 2 Empathy Map</figcaption></figure><p>This participant’s case highlights how administrative inefficiencies disproportionately burden chronic care patients. Even with deep knowledge of insurance processes, he is repeatedly tripped up by denials and unpredictable changes in accepted drug brands. Further the fact that he sometimes pays questionable bills simply to avoid conflict reflects a broader power imbalance. The system’s complexity makes patients feel that resistance is futile. Overall, he sees the U.S. healthcare system as profit-driven and unnecessarily burdensome, especially for seniors and people with chronic illnesses who need consistent care.</p><p><strong>Insight #1:</strong> Chronic care patients need stability in coverage (e.g. consistent coverage of specific insulin providers for diabetic patients) to maintain trust and health.<br><strong>Insight #2:</strong> Seniors want bills and coverage to be simpler, clearer, and more predictable, with advocates available to help them navigate denials.<br><strong>Insight #3:</strong> Systemic delays and poor communication create conditions where patients abandon disputes and pay unnecessary costs suggest the need for improved claim processes.</p><p><strong>Participant 3</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/0*W87_p56yGQnuqxwd" /><figcaption>Image from Student Health Center at Davidson College</figcaption></figure><p>The Student Health Center staff member interviewed works primarily on insurance verification, billing, and helping Davidson students understand their coverage. As an “extreme user” of the insurance system, they see billing issues daily and are often the first line of support for students struggling to interpret confusing paperwork. Unlike patients who encounter the system occasionally, this staff member interacts with it daily, making their perspective particularly valuable because it reveals not just isolated problems, but recurring breakdowns in how insurance and billing are designed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EuOwJQ3XuszEvB83CPcrmA.png" /><figcaption>Participant 3 Empathy Diagram</figcaption></figure><p>A striking pattern they noted is that many students misinterpret explanations of benefits (EOBs) as bills. Because these documents use jargon and often highlight large uncovered charges before adjustments are applied, students experience unnecessary panic, sometimes calling their parents. This suggests a design failure because communication materials are written for insurers and providers, leaving patients requiring an intermediary to interpret the document.</p><p>Another recurring issue comes from billing codes. A small coding difference, such as whether a sore throat visit is categorized as preventive or illness evaluation, can change the bill by hundreds of dollars. Students have no visibility or control over these decisions, yet they bear the financial consequences.</p><p>The staff also emphasized that students are reactive rather than proactive about insurance. Most only engage with the system once a problem arises. As a consequence, staff must not only fix billing issues but also provide crash-course education in how insurance works. This suggests that the system assumes a baseline literacy that students do not have.</p><p><strong>Insight #1:</strong> Students lack basic literacy around insurance, especially understanding EOBs, and need clearer, plain-language tools. Without redesigning communication, staff remain the only translators of a broken system.<br><strong>Insight #2:</strong> Small distinctions in how providers code each appointment, which is outside a student’s control, can cause hundreds of dollars in charges, pointing to systemic design flaws in billing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTKOXuaXsMsUaBwq7I_nqw.png" /><figcaption>Glossary of Health Coverage provided by Health Center</figcaption></figure><h3>Conclusion</h3><p>Conducting these interviews and carrying out the needfinding methodology allowed me to uncover recurring problems with how people experience health insurance and medical billing in the U.S. It also helped me identify patterns that cut across very different life stages and roles,</p><p>In particular an emerging pattern across these accounts is the emotional toll. Whether frustration, resignation, or mistrust, each participant interpreted recurring obstacles as evidence that the system is driven more by profit than patient care. Despite differences in age, role, and health status, they all highlighted the need for greater clarity, stability, and transparency in billing and insurance communication.</p><p>From these issues, I arrived at several insights:</p><ul><li><strong>Insight #1:</strong> Patients need clear, itemized bills that explain exactly what each charge is for, in plain language.</li><li><strong>Insight #2:</strong> Hospitals and insurers should prioritize informed consent by explaining procedures and test results before billing for them.</li><li><strong>Insight #3:</strong> Chronic care patients need stability in coverage (e.g. consistent coverage of specific insulin providers for diabetic patients) to maintain trust and health.</li><li><strong>Insight #4:</strong> Seniors want bills and coverage to be simpler, clearer, and more predictable, with advocates available to help them navigate denials.</li><li><strong>Insight #5:</strong> Systemic delays and poor communication create conditions where patients abandon disputes and pay unnecessary costs suggest the need for improved claim processes.</li><li><strong>Insight #6:</strong> Students lack basic literacy around insurance, especially understanding EOBs, and need clearer, plain-language tools. Without redesigning communication, staff remain the only translators of a broken system.</li><li><strong>Insight #7:</strong> Small distinctions in how providers code each appointment, which is outside a student’s control, can cause hundreds of dollars in charges, pointing to systemic design flaws in billing.</li></ul><p>Although these interviews represent only a small sample, they surface systemic flaws in medical billing that affect patients across contexts. Through this process I have gained a better understanding of how the system works across different life stages but also insights into the systems shortcomings and areas of possible improvement</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f3d6c23463c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>