<?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 karimot isiaka on Medium]]></title>
        <description><![CDATA[Stories by karimot isiaka on Medium]]></description>
        <link>https://medium.com/@isiakakarimot?source=rss-47b5e4716a37------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-9ko83kNy6yaJd5wkHol-w.jpeg</url>
            <title>Stories by karimot isiaka on Medium</title>
            <link>https://medium.com/@isiakakarimot?source=rss-47b5e4716a37------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:05:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isiakakarimot/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[From Research to Recommendations: Closing Out My LFX Mentorship]]></title>
            <link>https://medium.com/@isiakakarimot/from-research-to-recommendations-closing-out-my-lfx-mentorship-1cc23e22bdfe?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cc23e22bdfe</guid>
            <category><![CDATA[the-linux-foundation]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[opentelemetry]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Thu, 17 Sep 2026 22:20:42 GMT</pubDate>
            <atom:updated>2026-09-17T22:20:42.701Z</atom:updated>
            <content:encoded><![CDATA[<p>As my LFX Mentorship draws to a close, I find myself reflecting on how much this experience has changed me, not just as a designer, but in how I approach unfamiliar spaces.</p><p>When I started, OpenTelemetry and observability were largely new to me. What felt like a steep learning curve gradually became an opportunity to contribute from a UX and product design perspective.</p><p>After conducting user interviews and a competitive analysis of similar tools, the next step was to bring those findings together and think about what they meant for the OpenTelemetry Ecosystem Explorer.</p><h3>What the Research Revealed</h3><p>The research showed that users often struggle not because information doesn’t exist, but because finding the right information at the right time can be difficult. This shaped the direction of my Information Architecture work. I proposed a five-node baseline for component pages: Overview, Expected Telemetry, Semantic Convention Conformance, Configuration, and Version History.</p><p>The aim was to help users understand a component before they commit to using it, what it does, what telemetry it produces, how it aligns with relevant conventions, how configuration affects its output, and what has changed across versions. I also looked at how this structure could work across different ecosystems. Rather than forcing every ecosystem into the same taxonomy, the recommendation was to keep the component-level information structure consistent while allowing each ecosystem to reflect how its components are actually organized and distributed.</p><p>One of my mentors raised a follow-up question after reviewing the IA document: could Semantic Convention Conformance become its own discovery node, allowing someone exploring the GenAI space to find related OpenTelemetry libraries and compare their conformance?</p><p>Working through that question helped clarify the role of GenAI in the Explorer. Instead of creating a separate ecosystem branch that could duplicate existing content, the recommendation became a GenAI discovery and comparison layer. This would allow users to compare relevant libraries and then navigate to the component pages under the ecosystems where those libraries actually belong.</p><p><strong>Making the Work Reusable</strong></p><p>Beyond the IA recommendations themselves, one of my mentors suggested putting together a set of guiding principles for each ecosystem, distilling the requirements around version history and other dimensions like searchability.</p><p>I took that idea and brought the key decisions from my research and IA work together into a Guiding Principles for Ecosystems &amp; Component Pages document.</p><p>The principles turn the research into practical guidance for future work, covering areas such as discovery, expected telemetry, configuration, version history, semantic convention conformance, and the balance between information the Explorer should explain directly and information better supported through links to deeper documentation, source code, or long-form guides.</p><p><strong>Looking Back</strong></p><p>One of the biggest lessons I am taking away from this mentorship is that I don’t need to know everything before stepping into something challenging. I came into this project without an observability background. I had to learn a new domain, understand unfamiliar technical concepts, speak with people who use the technology, and eventually contribute recommendations to an open-source project. My interviewing itself got sharper over time too, thanks to consistent feedback from my mentors along the way.</p><p>I’m incredibly grateful to my mentors, Amy, Jay and Andrej, for making that possible. They created an environment where I felt comfortable asking questions, learning, and contributing. Their insights, feedback, and guidance were a huge part of helping me get here. I genuinely couldn’t have delivered this work without their support.</p><p>Although the mentorship is coming to an end, I’m looking forward to continuing to contribute to OpenTelemetry and seeing how the Ecosystem Explorer evolves, especially what it becomes for the people who use it.</p><p>I came into this mentorship trying to understand an unfamiliar ecosystem. I’m leaving with a real foundation in it, still plenty left to learn, a stronger user research and IA practice, and, most importantly, a stronger belief in what I’m capable of. Sometimes, you just need to step into the unfamiliar and give yourself the chance to learn.</p><p>This is the final post in a three-part series. You can read the first post <a href="https://medium.com/@isiakakarimot/mapping-opentelemetry-ecosystem-explorer-be218ae03075">here</a> and the second <a href="https://medium.com/@isiakakarimot/from-learning-the-domain-to-learning-from-users-82af433feb7a">here</a>.</p><figure><img alt="A hierarchical information architecture diagram for the OpenTelemetry Ecosystem Explorer. At the top is a blue node labelled “OpenTelemetry Ecosystem Explorer,” branching into five green navigation nodes: Search, Ecosystems, Signals, Recent Activities, and GenAI. The Ecosystems branch expands into three yellow nodes — OTel Collector, OpenTelemetry Java Agent, and Python — each drilling down through their respective components to individual component pages sharing a consistent five-node structure" src="https://cdn-images-1.medium.com/max/1024/1*mFlqedfR4w7oDL2EgnzOYA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cc23e22bdfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning the Domain, Speaking to Users]]></title>
            <link>https://medium.com/@isiakakarimot/from-learning-the-domain-to-learning-from-users-82af433feb7a?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/82af433feb7a</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[opentelemetry]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[cncf]]></category>
            <category><![CDATA[lfx-mentorship]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 07:47:45 GMT</pubDate>
            <atom:updated>2026-08-27T12:40:39.663Z</atom:updated>
            <content:encoded><![CDATA[<p>In my <a href="https://medium.com/@isiakakarimot/mapping-opentelemetry-ecosystem-explorer-be218ae03075?sharedUserId=isiakakarimot">previous blog post</a>, I shared my onboarding experience into the LFX Mentorship Program and how I was beginning to understand the OpenTelemetry ecosystem and the problem the Ecosystem Explorer is trying to solve.</p><p>Over the past few weeks, my work has shifted from learning about the domain to also learning from the people who use it every day.</p><p>I’ve been conducting UX research to better understand how developers and observability practitioners discover, evaluate, and use information about OpenTelemetry components. Alongside that, I’ve also been exploring how similar technical platforms organize large amounts of documentation and metadata to support users in finding the information they need.</p><p><strong>Learning from Existing Platforms</strong></p><p>One of the research methods I used was a competitive analysis of technical documentation and package discovery platforms, including npm Registry, Artifactshub, Crates.io, Docker Hub, Go Package site and the Ecosystem Explorer itself.</p><p>I understand that competitive analysis isn’t about copying what other products are doing. It’s about understanding patterns that users have already become familiar with. I looked out for how these platforms organize large amounts of technical information. How they help users navigate between versions. How they surface the most important information.</p><p>Two patterns stood out to me. Search navigation is prioritized across platforms, making it easier for users to quickly find what they need. The second was how these platforms pair technical metadata with the primary content, surfacing information such as versions, maintainers, dependencies, and other package details alongside the main documentation.</p><p>Studying these platforms has already given me useful ideas about different approaches to navigation, search, filtering, versioning, and information organization that I’ll later consider when developing Information Architecture recommendations for the Ecosystem Explorer.</p><p><strong>Talking to the People Behind the Code</strong></p><p>Before speaking with participants, I developed a <a href="https://github.com/open-telemetry/opentelemetry-ecosystem-explorer/blob/main/projects/ux-research-and-info-arc/research-plan.md">research plan</a>, drafted an <a href="https://github.com/open-telemetry/opentelemetry-ecosystem-explorer/blob/main/projects/ux-research-and-info-arc/user-interview-discussion-guide.md">interview guide</a>, and worked closely with my mentors to refine both the questions and the participant recruitment process.</p><p>We eventually spoke with seven participants whose backgrounds ranged from software engineers and software architects to Site Reliability Engineers (SREs) and observability specialists. Although their roles and levels of experience varied, most of them relied on OpenTelemetry in their day-to-day work, giving me the opportunity to understand how different users approach similar problems.</p><p><strong>One Thing That Surprised Me</strong></p><p>Before beginning the interviews, I thought that discoverability would mainly be a challenge for people newer to OpenTelemetry, that experienced users would know where to look, but that was not exactly the case.</p><p>The issue wasn’t that documentation was missing. It was that even when they knew exactly what they were looking for, they didn’t always know where the most relevant answer lived. Finding it required searching across multiple pages, repositories, and external resources before they could be confident they had the right information.</p><p>Rather than relying on a single source, most participants moved between official documentation, Google, GitHub repositories, community discussions, AI tools, and blog posts. They pieced together information from multiple places before making implementation decisions, not out of preference, but because no single source consistently gave them everything they needed.</p><p>This told me that discoverability isn’t just about whether information exists, it’s about whether it’s connected. Users may not need more documentation, but it is obvious they need clearer paths to what already exists.</p><p><strong>Another Observation</strong></p><p>Another interesting finding was how participants used AI. Most of them used it to summarize documentation, explain unfamiliar concepts, generate code examples, or troubleshoot problems, but almost everyone emphasized the importance of verifying AI-generated answers against official documentation, GitHub repositories, or previous experience before acting on them.</p><p>That observation made me think differently about documentation. Rather than competing with AI, good documentation may increasingly need to complement it by providing information that AI can reliably reference and surface.</p><h3>Looking Ahead</h3><p>The next phase of the project is to synthesize these findings into Information Architecture recommendations for the Ecosystem Explorer.</p><p>The goal isn’t simply to reorganize documentation. It’s to better understand how people make decisions when working with OpenTelemetry and explore how information can be structured to support those decisions more effectively.</p><p>I’m looking forward to sharing what comes next.</p><figure><img alt="Figma affinity map from OpenTelemetry Ecosystem Explorer user research, organizing some participant responses into six theme columns: Use of AI, Discovering Info, Version-specific Info &amp; Changelogs, Telemetry to Expect, Choosing &amp; Configuring Components, and Beyond Reference Docs. Each row represents one anonymized participant’s color-coded sticky notes across the themes." src="https://cdn-images-1.medium.com/max/1024/1*HptUeMIjjTHmlSzQUiSu0w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82af433feb7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mapping OpenTelemetry Ecosystem Explorer]]></title>
            <link>https://medium.com/@isiakakarimot/mapping-opentelemetry-ecosystem-explorer-be218ae03075?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/be218ae03075</guid>
            <category><![CDATA[the-linux-foundation]]></category>
            <category><![CDATA[opentelemetry]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[cnfc]]></category>
            <category><![CDATA[lfx-mentorship]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Wed, 24 Jun 2026 10:32:14 GMT</pubDate>
            <atom:updated>2026-06-24T10:32:14.022Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently <a href="https://mentorship.lfx.linuxfoundation.org/project/9e72750b-a515-4cef-86c8-0ffcdcd39298">got accepted</a> into the LFX Mentorship Program, where I will be conducting UX research and Information Architecture work for the OpenTelemetry Ecosystem Explorer.</p><p>Over the past two weeks, my focus has been onboarding into a domain that was completely new to me: observability. My onboarding process has involved understanding the OpenTelemetry ecosystem, learning core observability concepts, exploring the current Ecosystem Explorer, and working closely with my mentors, whose guidance has shaped how I’m approaching this research from the very start.</p><p>Like many designers entering a technical space, I quickly discovered that understanding the user experience requires understanding the ecosystem itself. Before I could think about navigation, information architecture, or user workflows, I needed to learn what OpenTelemetry is, how instrumentation works, and how developers use telemetry data to understand the behavior of their systems.</p><h3><strong>The Challenge</strong></h3><p>As I began exploring the OpenTelemetry ecosystem, I noticed that information about instrumentation is often spread across multiple sources. Developers may look through documentation sites, GitHub repositories, package registries, vendor websites, community discussions, and increasingly, AI tools.</p><p>Even when users find the instrumentation they are looking for, important questions can remain unanswered:</p><ul><li>What telemetry will this instrumentation emit?</li><li>Which libraries or frameworks are supported?</li><li>How do configuration options affect the telemetry produced?</li><li>What changed between versions?</li></ul><p>These aren’t just my own early impressions — as reported in OpenTelemetry’s recent <a href="https://opentelemetry.io/blog/2026/introducing-the-ecosystem-explorer/">Ecosystem Explorer project update</a>, their 2025 Developer Experience Survey found that users often have to piece together information from multiple sources, and a separate Getting Started Survey found that 65% of respondents wanted reference implementations showing what instrumentations actually produce.</p><p>This creates a frustrating loop: to really know what telemetry a component will produce, you often have to deploy it first and see for yourself. That’s a lot to ask of someone who’s just trying to evaluate whether OpenTelemetry fits their needs. These are the kinds of questions the Ecosystem Explorer aims to help users answer before they get that far.</p><p>Understanding why those questions are so hard to answer required me to first understand the ecosystem itself.</p><p>My first real surprise during onboarding was that OpenTelemetry isn’t a single product. I initially assumed it was one unified system, but I quickly discovered that OpenTelemetry is made up of multiple ecosystems, components, and instrumentation approaches that vary significantly depending on the programming language and technology involved.</p><p>I also noticed that the Ecosystem Explorer isn’t trying to replace documentation. I thought it was simply another documentation site. As I explored it further, I realized its value lies in helping users discover and understand instrumentation before implementation, answering questions like what telemetry a component emits, what libraries it supports, and how configuration options affect the telemetry produced.</p><h3><strong>A Difference Between Ecosystems</strong></h3><p>One observation that stood out to me is that not every ecosystem is structured the same way.</p><p>The Java ecosystem centers around a single Java Agent that bundles instrumentation for hundreds of libraries and frameworks. A user might ask:</p><p><em>“What instrumentations are included in the Java Agent?”</em></p><p>Python works differently. Instead of a single unified agent, OpenTelemetry Python consists of many separate instrumentation packages. A user might instead ask:</p><p><em>“Which instrumentation packages do I need for my application?”</em></p><p>While these questions may seem similar, they suggest different discovery patterns and information needs. Understanding those differences will be an important part of my research throughout this mentorship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqMJF59iSBmMA8jhG5oCmw.png" /><figcaption>Information architecture of the current OpenTelemetry Ecosystem Explorer, mapped during onboarding.</figcaption></figure><h3><strong>What’s Next?</strong></h3><p>Over the coming weeks, I’ll be working closely with my mentors to dig into how users actually find and evaluate instrumentation today — whether through LLMs, GitHub, vendor docs, or trial and error, and what questions they’re really trying to answer along the way. I’ll also be looking at how different personas (app developers, platform engineers, SREs) approach this differently, and how other dense technical registries like npm, crates.io, and Docker Hub solve similar discovery problems.</p><p>This will take shape as user interviews, a competitive analysis, and eventually, concrete Information Architecture recommendations for how the Explorer presents component data as it grows. I’ll be sharing more as the research takes shape, with the next update around the midpoint of the mentorship.</p><h3><strong>References &amp; Further Reading</strong></h3><p>Get more details about:</p><p><a href="https://opentelemetry.io/docs/what-is-opentelemetry/">OpenTelemetry</a></p><p><a href="https://explorer.opentelemetry.io/">OpenTelemetry Ecosystem Explorer</a></p><p><a href="https://opentelemetry.io/blog/2026/introducing-the-ecosystem-explorer/">Introducing the Ecosystem Explorer Project</a></p><p><a href="https://github.com/open-telemetry/opentelemetry-ecosystem-explorer/issues/309">My LFX Mentorship Project</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be218ae03075" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Web Accessibility is Everyone’s Business]]></title>
            <link>https://medium.com/@isiakakarimot/why-web-accessibility-is-everyones-business-23b9aabb0c7d?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/23b9aabb0c7d</guid>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 06:35:42 GMT</pubDate>
            <atom:updated>2026-03-28T06:35:42.593Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine landing on a website to buy a gift, but the text is so faint it blends into the background. Or picture trying to check out on your phone, only to find the “Buy” button is hidden off-screen because the site is not responsive. For many, these are minor inconveniences; for others, these are the digital walls that make the internet inaccessible.</p><p>15% of the world’s population lives with some form of disability, according to the<a href="https://www.who.int/teams/noncommunicable-diseases/sensory-functions-disability-and-rehabilitation/world-report-on-disability"> World Health Organisation</a>, that is over one billion people navigating a web that was largely not built with them in mind.</p><p>Web Accessibility (A11y) is the practice of ensuring there are no barriers that prevent interaction with, or access to, websites by people with physical disabilities, visual disabilities, situational disabilities, cognitive or any form of disabilities. When we ignore accessibility, we are actively excluding people.</p><figure><img alt="A picture quote that says, “When we ignore accessibility, we are actively excluding people.”" src="https://cdn-images-1.medium.com/max/976/1*CLfZDcY8NpoKha1V_rv-AA.png" /></figure><h3>Major Impairments We Must Design For</h3><p>To build truly inclusive platforms, we must understand the diverse ways users experience the web. Disability is not a monolith, it manifests in various forms:</p><ul><li><strong>Visual:</strong> Including total blindness, low vision, and color blindness.</li><li><strong>Cognitive:</strong> Including dyslexia, ADHD, autism, or memory-related challenges.</li><li><strong>Hearing:</strong> Including deafness or being hard of hearing.</li><li><strong>Motor/Physical:</strong> Including limited fine motor control, tremors, or the inability to use a mouse.</li></ul><h3><strong>Practical Interventions</strong></h3><p>Inclusivity does not happen by accident; it happens by design. To meet the Web Content Accessibility Guidelines (WCAG), we apply specific interventions for different needs:</p><h3>1. Visual Accommodations</h3><ul><li><strong>High Contrast:</strong> Text-to-background contrast ratios must meet at least 4.5:1 for normal text — this is not a suggestion, it is the WCAG AA minimum.</li><li><strong>Screen Reader Optimization:</strong> Use semantic HTML so assistive technology can accurately describe the page. A &lt;div&gt; styled as a button is invisible to a screen reader. A real &lt;button&gt; announces its role, responds to keyboard events, and requires zero extra work.</li><li><strong>Alt-Text:</strong> Providing descriptive text for images. Alt-text is not a caption, it is a replacement. An image of a dark-skinned woman coding at a standing desk should not read alt=”image” or even alt=”woman at desk”. It should read alt=”A woman coding at a standing desk with dual monitors”. Specific enough that a blind user gets the same context a sighted user does at a glance. The rule: write what the image does for the reader, not what it is.</li></ul><h3>2. Cognitive &amp; Neurological Support</h3><ul><li><strong>Predictable Layouts:</strong> Consistent navigation across the site reduces the mental overhead of reorienting on every page.</li><li><strong>Readability Tools:</strong> Offer distraction-free modes or abstractive summaries that surface the key points without overwhelming detail.</li><li><strong>Alternative Inputs:</strong> Provide audio versions of long-form text for users who process information better by listening than reading.</li><li><strong>Use Readable Fonts</strong>: Use clear, legible typefaces, the goal is a font the brain parses automatically, not one it has to decode.</li></ul><h3>3. Hearing &amp; Auditory Access</h3><ul><li><strong>Captions &amp; Transcripts:</strong> Clear, intentional captions are essential for all video and audio content. Auto-captions are a starting point, not a finish line, they regularly miss technical terms, names, and accents.</li><li><strong>Visual Indicators:</strong> Never rely on sound alone for alerts. Every audio cue must have a visible equivalent, a banner, a badge, a flash, so deaf and hard-of-hearing users receive the same information.</li></ul><h3>4. Motor &amp; Physical Accessibility</h3><ul><li><strong>Keyboard Navigation:</strong> Every action, every link, every form field must be reachable using only Tab, Enter, and Space. If it requires a mouse, it excludes someone.</li><li><strong>Large Touch Targets:</strong> Buttons must be large enough for users with tremors or limited dexterity, WCAG recommends a minimum 44×44px touch target.</li><li><strong>Voice Control:</strong> Ensuring the site is compatible with software like Dragon NaturallySpeaking,which lets users navigate and dictate entirely by voice, no keyboard or mouse needed.</li></ul><h3>Curb-Cut Effect</h3><p>Sidewalk ramps were designed for wheelchairs. But they ended up helping parents with strollers, delivery workers with carts, and travelers hauling heavy luggage. Nobody planned for that. It happened because good design for a constrained user is quietly good design for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ECuYhmSPwni6rr-TkoBuzg.jpeg" /><figcaption>Image Credit — Freepik</figcaption></figure><p>Web accessibility works identically. High-contrast text was designed for users with visual impairments, it also helps someone reading in bright sunlight. Captions became important for those with hearing loss, but it helps someone watching a video in a quiet library. Keyboard navigation was built for users who cannot operate a mouse, today it helps a user who simply moves faster without one. Voice control was originally created to help those with vision loss and limited mobility operate devices without a mouse, it is now used for different purposes like hands-free navigation while driving and controlling smart homes.</p><p>Build for the hardest constraint and you raise the floor for everyone.</p><p>The web was imagined as a place without gatekeepers, where geography, status, and circumstance would not determine who gets access to information. Disability should not be the exception to that promise. Build like everyone is watching. Because everyone should be able to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23b9aabb0c7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Designed an Internal CMS for a Global Humanitarian Team]]></title>
            <link>https://medium.com/@isiakakarimot/how-i-designed-an-internal-cms-for-a-global-humanitarian-team-0be58cdcf2c0?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/0be58cdcf2c0</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[commit-global]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 11:04:27 GMT</pubDate>
            <atom:updated>2026-01-19T11:37:51.698Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d3OqzsAcousgK0GGfmZqgA.png" /><figcaption>Cover image for the case study</figcaption></figure><p><strong><em>My Role: </em></strong><em>User Research, UX Design, UI Design, Design Documentation, Concept Mapping, Developer Handoff.</em></p><p><strong><em>Contributor: </em></strong><a href="https://medium.com/u/284201b065d8"><strong><em>Mojetioluwa D. Ewetola</em></strong></a><strong><em> </em></strong><em>(UX Research, User Flow, Low-Fidelity Wireframe)</em></p><p><strong><em>Tools: </em></strong><em>Figma, Miro</em></p><h3>Introduction</h3><p><strong>Commit Global</strong> is a civic tech nonprofit that builds digital tools for humanitarian and social impact. The <strong>PTSD Help mobile app</strong> provides mental health resources and support to individuals experiencing trauma, but updating its content required developer intervention for every change, creating bottlenecks and limiting the team’s ability to respond quickly to user needs.</p><p>I joined a team of UX interns tasked with designing an internal <strong>Content Management System (CMS)</strong> that would empower non-technical staff like the content managers, to manage app content independently.</p><h3>Design Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmDYGKJv8Edqina5ughOuw.png" /><figcaption>The Design Process</figcaption></figure><h3>The Discovery Phase</h3><p>At this stage, we needed to understand who we were designing for and why it matters. During the discovery phase, our goal was to meet with every stakeholder that mattered to the project. We met with the product team. We met with the developers to understand what was technically feasible. We had meetings with the content managers who are the primary users of the CMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_wajVLaCLmMky4pcAKIAw.png" /><figcaption>Insights gathered and pain points identified during stakeholder interviews</figcaption></figure><h3>Define</h3><h4>The Problem Statement</h4><p><strong>Updating an app’s content should not require waiting on engineers to get it done. </strong>Yet this was the reality for the PTSD Help app. Every content update, no matter how small, required developer intervention. Content managers and stakeholders had no direct access to manage the app’s mental health resources, multilingual text, or educational materials.</p><p>For a tool addressing mental health and trauma, <strong>responsiveness is critical</strong>. The organization needed to empower internal teams to manage content directly, eliminating engineering bottlenecks and enabling the app to scale its humanitarian impact efficiently.</p><h4>The Solution - Internal CMS</h4><p>The Commit Global team wanted to solve this problem with an internal CMS that is easy to use for content updates. The main content categories that need to be updated are:</p><ul><li>The Tools</li><li>The Learning Resources</li><li>The Support</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YKBIqjXWlzjP86xgmf-1-A.png" /></figure><h4>User Flow</h4><p>The Content Manager is able to log in and :</p><ul><li>Switch between countries whose content they want to edit on the dashboard</li><li>Navigate to the main content categories</li><li>See the latest content updates</li><li>Update content and save</li><li>Create and edit article in the Learn Category</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G0DJ3u98IsIAlO627qMGhg.png" /></figure><h4>Design</h4><p><strong>Wireframe</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UO0XlbQpvQ2pOINwat1jNg.png" /><figcaption>The low-fidelity wireframe of the dashboard started like this</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jM0RatmcsvZ53buJ9YGk6g.png" /></figure><p>Because there are more than two countries, the interface of the dashboard had to change. It was reimagined and placed above the menus on the side, and the recently updated content is highlighted instead. It looks more like a dashboard this way.</p><p>A couple of things were moved around and improved upon as we move to the high-fidelity prototype design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wf7ooinuJ1xPph2KjgXTIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*livjqCXuJ2AmBaWRtGwEug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sOZjzHoLJ07hLw5eJG7hdg.png" /></figure><p>I single-handedly worked on the <strong>high-fidelity UI design</strong>. Here are a couple of things I improved upon for a better user experience for the team members who will use the custom CMS internally:</p><ol><li>Easy navigation. The Country switch is at the top to allow the content editors switch to which country whose content they want to edit or update. The <strong>tools</strong> and the <strong>learn </strong>section of the PTSD app carry most of the content that need to be updated. I placed them on the left menu for easy access.</li><li>Custom design for each section. The Tools and the Learn section of the app work in different ways. While the Tools content structure is fixed, the Learn section is a quite flexible. In the Learn Section, new articles can be created and available content can be edited and updated.</li><li>Minimalist UI. In order to make the work of the internal team easier, the choise of UI design was intentionally clean and clutter-free. This is a CMS that will house the content that affects lives of people across countries. It is important that the design makes it easy for the team to get the work done without confusion.</li><li>Button were updated. One of the buttons in the content edit environment was changed from Preview to Cancel. Since a content preview will not be needed in this case, we made room for some flexibility to allow the content managers to save or cancel.</li></ol><h4>More UI screens</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_tc7ugsSERJdwmwEO4VIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mjxL4HbohFDaZZrjUXmbog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mAiMJeqzbxxhXRAKaKFEbg.png" /></figure><p>I also added some annotations to help the developers better understand the flow of the design. During my presentation/developer handoff, the CTO (Chief Technology Officer) dropped “Good job” in the chat box.</p><p>It was really beautiful working on this project. A big shout-out to <strong>Teodora, (the Lead Product Designer of Humanitarian Digital Infrastructure at Commit Global</strong>) for her feedback and supervision during this project.</p><p>The CMS design has been handed off to developers and will soon enable content teams to manage the PTSD Help app’s resources across multiple countries independently.</p><p>Want to discuss your next project or collaborate? Connect with me on <a href="https://www.linkedin.com/in/karimotisiaka/">LinkedIn</a> or shoot me an email at isiakakarimot@gmail.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0be58cdcf2c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Breakdown: Building a Journaling App That Actually Works for Neurodivergent Minds]]></title>
            <link>https://medium.com/@isiakakarimot/product-breakdown-building-a-journaling-app-that-actually-works-for-neurodivergent-minds-eb6e3c8f3b4f?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb6e3c8f3b4f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[adhd-support]]></category>
            <category><![CDATA[prd]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Fri, 04 Jul 2025 16:39:42 GMT</pubDate>
            <atom:updated>2025-07-04T16:39:42.924Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A paper wireframe image from Pexels.com" src="https://cdn-images-1.medium.com/max/1024/1*kFD8-XhNwO-vdXtA4dHAfQ.jpeg" /><figcaption>Picture from pexels.com</figcaption></figure><h3>Product Overview</h3><p><strong>Mindnager</strong> is a mobile-first journaling and emotional tracking app designed specifically for individuals with ADHD and related neurodivergent conditions. It helps users externalize their thoughts, track moods and triggers, and build emotional self-awareness through structured yet flexible journaling prompts and visual mood history.</p><h3>Target Audience</h3><ul><li>Teens, young adults, and adults (ages 15–40) with ADHD or executive functioning challenges.</li><li>Neurodivergent users looking for a low-pressure, non-linear journaling experience.</li></ul><h3>Problem Statement</h3><p>People with ADHD often struggle with emotional regulation, memory, and building reflective habits. Traditional journaling apps are either too open-ended (causing paralysis) or too rigid (causing frustration). Emotional tracking is often isolated from daily reflection.</p><p><strong>Mindnager</strong> addresses this gap by offering a guided, distraction-friendly journaling experience with built-in emotional check-ins and visual feedback that supports self-regulation and pattern recognition.</p><h3>User Personas</h3><p>Persona one</p><figure><img alt="Maya is a 23-year-old university student with ADHD who needs gentle prompts and calming visuals to help her reflect on emotions without feeling overwhelmed.”" src="https://cdn-images-1.medium.com/max/1024/1*kSC_z0qjmwxHXT5ohCu1xw.png" /></figure><p>Persona two</p><figure><img alt="Jordan is a 38-year-old UX designer with ADHD who needs a simple, unified space to quickly track moods and thoughts without distraction." src="https://cdn-images-1.medium.com/max/1024/1*TTZ_0F2aI4_kpIebjcDAkw.png" /></figure><h3><strong>Core Features</strong></h3><ol><li><strong>Mood Check-in Wheel</strong></li></ol><ul><li>Users rate their current emotional state using a color-coded mood wheel.</li><li>Optional tags: energy level, triggers, context (e.g., “after work meeting”).</li></ul><p><strong>2. Guided Journal Prompts</strong></p><ul><li>Curated daily questions based on emotion logged (e.g., “You marked ‘anxious’ — what might be contributing to that today?”).</li><li>Option to write freely or select multiple-choice reflections.</li></ul><p>3. <strong>Guided Journal Prompts</strong></p><ul><li>Users can record quick thoughts and transcribe them later.</li><li>Helpful for those with writing fatigue or time constraints.</li></ul><p>4. <strong>Mood Timeline</strong></p><ul><li>Visual mood charts over days/weeks.</li><li>View patterns by time of day, tags, or emotional categories.</li></ul><p>5. <strong>Reminders &amp; Gentle Nudges</strong></p><ul><li>Smart notifications based on usage patterns (e.g., “You felt overwhelmed around this time yesterday — want to check in?”).</li><li>Calming, friendly tone (no guilt-based nudging).</li></ul><p>6. <strong>Privacy/security</strong></p><ul><li>Journal lock with unique user code.</li></ul><h3><strong>Use Cases</strong></h3><p><strong>Use Case 1: Quick Emotional Check-In</strong></p><ol><li>User opens app after a stressful meeting.</li><li>Taps “Check-in”.</li><li>Selects mood: “Frustrated”.</li><li>App asks: “What’s on your mind?” — offers guided prompts.</li><li>User logs a quick journal response.</li><li>Mood timeline updates.</li></ol><p><strong>Use Case 1: Quick Emotional Check-In</strong></p><ol><li>App reminds user at 9:00 PM: “How was your day?”</li><li>User taps notification.</li><li>Records 1-minute voice journal → transcribed.</li><li>Views emotional summary of the day.</li><li>Tags entry with “low energy” and “social fatigue”.</li></ol><p><strong>Success Metrics</strong></p><ul><li><strong>Daily Active Users (DAU)</strong>: % of users engaging with check-ins or journaling daily.</li><li><strong>Journal Completion Rate</strong>: % of users completing a prompt after a mood check-in.</li><li><strong>Retention Rate (7-day, 30-day)</strong>: Are users building a habit?</li><li><strong>Mood Insight Usage</strong>: How often users view timeline/history or reflect on patterns.</li><li><strong>Average Session Duration</strong>: Time spent per entry — is the flow too long or short?</li></ul><h3>Assumptions and Constraints</h3><p><strong>Assumptions:</strong></p><ul><li>Users value privacy and may not want cloud-based syncing by default.</li><li>ADHD users prefer minimal distractions and reduced friction to log thoughts.</li><li>Emotional awareness tools are more effective when visually intuitive.</li></ul><p><strong>Constraints:</strong></p><ul><li>Voice transcription costs may affect free tier scalability.</li><li>Must work offline (due to privacy and accessibility concerns).</li><li>Need for accessibility features (e.g., dyslexia-friendly fonts, dark mode) from the start.</li><li>High abandonment rate for complex setup processes</li><li>Users prefer visual cues over text-heavy instructions</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb6e3c8f3b4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your life has meaning and your contribution matters]]></title>
            <link>https://medium.com/@isiakakarimot/your-life-has-meaning-and-your-contribution-matters-fca8c114d731?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/fca8c114d731</guid>
            <category><![CDATA[makoko-lagos]]></category>
            <category><![CDATA[selfesteem-selfconfidence]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[confidence-builder]]></category>
            <category><![CDATA[building-confidence]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Wed, 18 Jun 2025 21:31:02 GMT</pubDate>
            <atom:updated>2025-06-18T21:31:02.109Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Karimot with the pupils of Makoko Children Development Foundation" src="https://cdn-images-1.medium.com/max/1024/1*bZrWLxigr5nXxa8WshtrTQ.jpeg" /><figcaption>Karimot with the pupils of <strong>Makoko Children Development Foundation</strong></figcaption></figure><p>Growing up, I was quite bold until my confidence took a devastating fall just before I became a teenager. By the time I entered my teenage years, it had gotten much worse. I vividly remember our individual English presentation in secondary school. Everyone presented but me. I stood in front of the class completely silent — even the quietest person in our class had managed to say something. As I remained wordless, my teacher simply called the next person, and I walked back to my seat with feelings I still can’t fully describe. Was it shame? Relief? Perhaps both.</p><p>By the time I reached university, I knew something had to change. I couldn’t continue living like this. “Karimot,” I told myself, “you need to go back to the real you — the Karimot who was easily noticed because of her voice. The one who was bold, who spoke up, who even corrected adults despite being just a child. The girl who volunteered to represent her class in debates even when she wasn’t selected.”</p><p>It started with that moment of brutal honesty with myself — making the conscious decision to become bold again, to speak up instead of staying silent when I had something to say. Gradually, by taking small steps, things began to change. I started volunteering, and through those experiences, I was thrust into situations that forced me to learn public speaking. This taught me a fundamental truth: the only way to truly learn something is by doing it, not just reading tips about how to do it.</p><p>Today, I had the privilege of visiting <a href="https://www.mcdf.ng/"><strong>Makoko Children Development Foundation</strong></a> to speak with Grade 4 and 5 students about building confidence. The session was wonderfully interactive, and I was thrilled to see many of them introduce themselves to the class and summarize what they had learned. Before leaving, I donated a few copies of my book “<strong>Confidence Within</strong>” to their library, ensuring they can access these lessons whenever they need them.</p><figure><img alt="I and two of Grade 5 students with a copy of my book, “Confidence Within”" src="https://cdn-images-1.medium.com/max/1024/1*915bki9pnfh-bv70F_PiPA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBwJ-hO_z_7v8m6mhu9iQg.jpeg" /><figcaption>Karimot speaking to the pupils</figcaption></figure><p>From the girl who couldn’t speak in front of her English class to someone now empowering others to find their own voices. This journey reminds me that our struggles can become parts of our greatest strengths, and our healing can become a source of hope for others. Alhamdulillah (All praise is due to Allah).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fca8c114d731" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing with Depth: Empathy, Impact, and Accessibility in UX]]></title>
            <link>https://medium.com/@isiakakarimot/designing-with-depth-empathy-impact-and-accessibility-in-ux-4d4059e7b410?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d4059e7b410</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Wed, 07 May 2025 14:59:03 GMT</pubDate>
            <atom:updated>2025-05-07T14:59:03.517Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QHNxjxCuj1fQUSM-QKbGLQ.jpeg" /></figure><p>As I grow in my journey as a User Experience Designer, I’ve realized that much of my work centers on one core principle: deep consideration for others and the positive impact I can make through thoughtful design.</p><p>Earlier this year, I completed my internship at the Wikimedia Foundation, where my focus was on enhancing the learning experience for people with various impairments. The work involved understanding how to create inclusive, accessible designs for individuals with visual, cognitive, motor, hearing, and non-motor impairments. This experience didn’t just improve my technical skill set, it profoundly deepened my empathy.</p><p>We often talk about empathy in UX, listening to users, identifying their pain points, and solving for them. But there’s a deeper level of empathy that comes from intentionally designing for people who interact with the web in ways we might not expect. True inclusion means making room for users who experience the world differently from the default assumptions baked into most digital products.</p><p>As a designer, the next time you begin a new project, I invite you to pause and ask:<br> <strong>How does a person who is differently abled fit into this experience?</strong></p><p>That question alone can unlock a world of design possibilities that serve more people, more meaningfully.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d4059e7b410" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Design in my Words]]></title>
            <link>https://medium.com/@isiakakarimot/product-design-in-my-words-86b9300de856?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/86b9300de856</guid>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Tue, 21 Jan 2025 04:23:51 GMT</pubDate>
            <atom:updated>2025-01-21T04:23:51.982Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Two large monitors on a table, with one screen showing wireframes and the other showing a collection of highfidelity designs." src="https://cdn-images-1.medium.com/max/1024/1*q99F8dKzyaO2MO5B3k77Lg.jpeg" /></figure><p>Let me explain product design through a real-world scenario: Cheryl is a video editor who uses a video app called <strong>Vidadite</strong> to edit videos for clients. After a year of delivering excellent edited videos using the app’s basic features, she discovered that some advanced features had been monetized. Recognizing the value these premium features could bring to her work, Cheryl decided to subscribe to the premium version. This exemplifies how a well-designed product can meet user needs while generating revenue for the company, as <strong>Vidadite</strong> has paying subscribers across different countries.</p><p>The product was strategically designed to meet the needs of professionals like Cheryl. Before launch, extensive user research would have been conducted, including user interviews, market analysis, and competitor research. This research continues post-launch through user feedback, behavior analytics, and usability testing to ensure the product evolves with user needs and market demands.</p><p>Product designers work in an iterative cycle of design, test, learn, and improve. They must consider multiple aspects: the user interface (UI) design for intuitive navigation, user experience (UX) design for seamless interactions, accessibility for users with different abilities, technical feasibility of features, and market viability of the product.</p><blockquote>According to the <a href="https://www.interaction-design.org/literature/topics/product-design?srsltid=AfmBOooW6yRKMgU7SK97bQVUnDGPKXzkVsWujmKG90ZAQ7nfnDPsxvf9">Interaction Design Foundation</a>, product designers work to optimize the user experience in the solutions they make for their users — and help their brands by making products sustainable for longer-term business needs.</blockquote><p>In my words, product design is the intentional creation of an experience that helps users achieve their goals while ensuring business success. It’s a balanced approach to solving user problems and meeting their needs while achieving business objectives through various monetization strategies like freemium models, subscriptions, or one-time purchases. The process requires deep understanding of user behaviors, pain points, and aspirations, combined with business acumen to create sustainable and profitable solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86b9300de856" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Community Stakeholders involved in digital learning for the young generation.]]></title>
            <link>https://medium.com/@isiakakarimot/getting-community-stakeholders-involved-in-digital-learning-for-the-young-generation-bb658b8e3f34?source=rss-47b5e4716a37------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb658b8e3f34</guid>
            <category><![CDATA[oppia]]></category>
            <category><![CDATA[oppia-foundation]]></category>
            <dc:creator><![CDATA[karimot isiaka]]></dc:creator>
            <pubDate>Thu, 21 Mar 2024 16:21:07 GMT</pubDate>
            <atom:updated>2024-04-01T03:52:12.571Z</atom:updated>
            <content:encoded><![CDATA[<p>Oppia is making young learners love Maths through its story based lessons and the impact is clear to see. I was recommended by a respected educator to speak to the management of Dornnie Private School about Oppia. After some phone conversations, the school management agreed for me to come implement a pilot in their school. The interesting thing is that I also got to show all their teachers how to use the Oppia App. I can confirm that ten out of eighteen teachers downloaded Oppia and the rest visited the Oppia website on their device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBO5QIbaAdatSPaVWSVnKA.jpeg" /><figcaption>Introducing the teacher to Oppia</figcaption></figure><p><strong>Implementing Oppia.</strong></p><p>When I got to Dornnie Private School on Friday Morning, 15th of March, 2024. I was welcomed by the school’s HeadMistress who informed me that the school Manager will be joining me soon. Truely, she joined us some minutes later. We had a brief meeting with the teachers, I spoke to them about Oppia and how it can benefit their pupils and I got to answer some of their questions. During the meeting we agreed on the classes that I would be conducting the pilot with and we ended up with Basic 4,5 &amp; 6.</p><p>The students were 31 in numbers combined and a topic they have all done in common was selected to give them a fair ground especially during the PreTest. A PreTest on <strong>Place Value</strong> was conducted and I had to write the question on the board for them. After their scripts have been submitted. I decided to take them on a <strong>Place Value</strong> lessons. After a short break, the PostTest was conducted. The story of Jamie really piqued their interest and they were excited to learn about his score in the Arcade game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RCbUaUd32kIK4yuDmzJwEw.png" /><figcaption>A screenshot of Oppia website showing the story based lessons on Place Value</figcaption></figure><p><strong>Key Observation.</strong></p><p>I observed that some of the students mixed up the order of place value from ten thousands to ones. But while we went through the Oppia lesson, I noticed how they took turns to eagerly answer the questions in the lessons. Sometimes, they gave the answer in chorus.</p><p>The students get super excited every time they get an answer correctly while taking the lessons.</p><p>All the learners wanted to either be the one to input the answer or submit the answer. I decided that they take turns to do so, in each group. Most of the teachers including the Headmistress donated their phones, they were paired in groups of 4 to 5 to use a device, this made it possible for everyone to participate actively.</p><p>31 students participated in the PreTest that conisted of 11 questions. While 29 students participated in the PostTest because their parents came for them earlier. Also, the school closed before we while we were about to complete the PostTest questions, so I had to stop at number 9 instead of 11. The charts below show how their test score increased significantly in the PostTest. The results are represented by the blue lines in the first and second charts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*rbAGw2nkLcTBvKXH_7j--Q.png" /><figcaption>The analysis of the PreTest(in blue) and PostTest (in red)</figcaption></figure><p>Success stories</p><p>After the pilot session, I was led to the School Manager’s office. She asked that the teachers who were present during the pilot should come in and they all had good things to say. The school manager said, “We will be expecting you next term. Please keep in touch with the Headmistress ”. The Headmistress said they will invite me from the third week so I can show the teachers around the Oppia website and they can continue from there.</p><p>The following Monday, I went back to the school to return the PreTest and PostTest results as requested by the Headmistress. I got a call a week later from the School Manager, who said <strong>“We need to introduce Oppia to our JSS1 students”.</strong></p><p>I look forward to keeping the conversations going with the management of Dornnie Private Schools. If you know a school or any organisation working to make quality education accessible to young learners, kindly tell them about Oppia. The App is available for download on <a href="https://play.google.com/store/apps/details?id=org.oppia.android">Android </a>devices and you can visit <a href="https://www.oppia.org/"><strong>Oppia.org</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb658b8e3f34" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>