The main stakeholders were Porchlight's founding and product leadership, who needed market evidence to validate or challenge early assumptions before committing engineering time. Product managers used the findings to sequence the roadmap. Design was a close second audience: the recommendation to prioritize a modern interface only holds up if it's grounded in a concrete account of what "dated" looks like across ten real competitors. Engineering leadership weighed in on feasibility, especially keeping AI-assisted features human-reviewable and auditable. Direct-care staff, house managers, and compliance officers weren't interviewed in this phase, but they're the ultimate beneficiaries of whatever gets built.

• Conducted a competitive and market analysis across ten care-operations platforms
• Evaluated each platform's interface design, feature coverage, and AI capabilities
• Built workflow maps that translated competitive findings into product requirements
• Partnered with product, design, and engineering leadership on positioning and prioritization

Competitive and market analysis was the right method. The question wasn't yet what users need specifically, but what's already been tried and where it fell short. I reviewed ten existing care-operations and resident-management platforms serving residential care and adjacent compliance-heavy sectors, scoring each against interface design, workflow coverage, and AI use. Findings fed into workflow mapping that turned competitive observations into buildable requirements.

• Dated interfaces. Dense forms, unclear navigation, little evidence of ongoing design investment, close to the market norm rather than a couple of laggards.
• Almost no AI. Documentation, summary drafting, and compliance form completion stayed manual across nearly the entire competitive set.
• A real but conditional gap. Dated interfaces plus an AI vacuum point to genuine whitespace, but only if AI stays reviewable and auditable; unreviewable AI is a liability in a regulated industry.

• Prioritize a modern, staff-first interface as the baseline differentiator
• Pair it with AI-assisted features (shift notes, summaries, compliance forms) that stay human-reviewed and fully auditable by design
• Build audit trails, source citation, and role-based access into AI capabilities from day one
• Give product and engineering a shared, evidence-based rationale for positioning heading into development

Net effect: the competitive findings were adopted directly into Porchlight’s product roadmap, giving leadership the green light to move forward on AI-assisted features with compliance built in from the start, not retrofitted later.

Plyr's founders were the most direct stakeholders and the primary audience for this research, since at an early-stage startup, roadmap and pricing decisions sit close to founder judgment. Product and design were the second core audience: deprioritizing interface polish in favor of billing clarity is a real reallocation of time, and needed to hold up on evidence. The fifteen club athletes who took part were a stakeholder group in their own right, representing the demand side of Plyr's target user base. Scouts, agents, and coaches sit further downstream as the platform's other core audience.

• Directed diary studies and in-depth interviews with fifteen club athletes
• Ran a competitive analysis of leading sports and athlete-focused platforms
• Synthesized findings into roadmap priorities adopted by product and design
• Partnered with founders on validating product concepts and prioritizing features

I directed a diary study paired with in-depth interviews across fifteen club athletes. Diary studies were the deliberate choice, since the question was about how expectations evolve and a single interview would only capture one moment. Interviews went deeper on behaviors the diary entries surfaced but couldn't fully explain. A competitive analysis benchmarked Plyr against other leading sports platforms.

• Engagement held steady. No early spike and taper, the pattern you'd expect from novelty rather than real staying power.
• Feedback skewed toward requests, not complaints. A sign the core experience already worked well enough that attention shifted to what's next.
• Interface friction barely came up. What athletes raised repeatedly, unprompted, was confusion around subscription and billing instead.

• Reallocated design and engineering focus toward subscription flow, pricing transparency, and value communication
• Deprioritized further interface polish in favor of the area where athlete concern actually concentrated
• Established a lightweight, ongoing channel for capturing athlete feedback rather than a closed, one-off study

Net effect: within the following sprint cycle, engineering and design priority shifted away from interface polish and toward the billing and subscription flow athletes were actually struggling with.

Product managers were the primary stakeholders, since the business case rested on retention and monetization tied to onboarding drop-off. UX/UI designers were the second core audience, translating behavioral findings into interface patterns. Front-end engineers were consulted on what was technically feasible to ship. The 150 participants, freshmen and sophomores navigating early career decisions, were the population this engagement aimed to represent accurately, though NDA terms limit how much specific input can be shared.

• Diagnosed the causes behind onboarding drop-off and inconsistent return usage
• Fielded and thematically analyzed a 150-participant engagement survey
• Explored gamification strategies grounded in retention research
• Aligned recommended game mechanics to the app's career-readiness goals

Primary methods were a survey and interviews, with A/B testing as a secondary method to pressure-test gamification concepts. I fielded the survey to 150 freshmen and sophomores, gathering data on usage habits and what drove or blocked engagement. Interviews added depth; responses went through thematic analysis, and A/B testing evaluated a shortlist of concepts directly. The screens developed alongside this research applied the Octalysis gamification framework across job discovery, XP and reward mechanics, streak tracking, and in-app messaging.

• Reward mechanisms meaningfully moved engagement. Participants returned more when actions were met with visible recognition tied to real progress, not novelty.
• Social and progress feedback rivaled core functionality. Participants valued seeing their own progress almost as much as the app's actual features.

• Progress indicators tied to meaningful steps like application status or career readiness
• Recognition tied to genuine milestones: completed profile, first application sent, interview prep finished
• Structured, goal-oriented task flows breaking the job search into achievable steps

Net effect: the findings narrowed the product team’s gamification plan from a broad feature wishlist to a focused set of progress and recognition mechanics, tied directly to return visits, the platform’s core retention metric.

Native speakers, language learners, and professional translators were interviewed not just as research subjects but as the people whose future participation the whole platform concept depended on. The broader stakeholder group included the initiative's founding team, who needed the research to validate whether a community-driven repository was worth building, and prospective content contributors and technologists who'd eventually build the platform. Swahiliverse didn't exist yet; the research itself became the platform's founding rationale.

• Conducted twelve interviews across native speakers, learners, and translators
• Ran a competitive UX analysis of six Swahili digital glossaries and dictionaries
• Mapped pain points around dialect visibility and meaning gaps
• Built personas covering translators, learners, dialect speakers, and technologists

I conducted twelve interviews across three groups: five native speakers, four learners, three professional translators, intentionally, since a repository designed around only one perspective risks missing what others need to trust and adopt it. In parallel, I ran a competitive UX analysis of six widely used Swahili glossaries, assessing layout, contextual examples, contributor transparency, and whether each tool supported exploration or only direct lookup.

• Explanatory depth mattered more than flat definitions. Participants wanted understanding, not just an answer.
• Cultural context built trust. Definitions grounded in cultural and linguistic context were trusted far more than isolated facts.
• Native speakers expected dialectal distinctions. A single "correct" translation actively undermined credibility with this audience.

• Exploration-based navigation with domain filters and related-content suggestions, replacing simple lookup
• Content layout separated into distinct sections for definitions, examples, dialects, and contributor notes
• Trust and credibility signals (contributor roles, verification, metadata) built in as core interface elements
• A modular, expandable information architecture able to grow without collapsing into clutter

Net effect: the research became the founding team’s go/no-go evidence, directly informing the decision to build Swahiliverse as a new platform rather than retrofit an existing glossary model.