Summary
You’ll have evidence you can quote in sprint planning, plus a ranked list of changes the team can start shipping in the next sprint.
We’ll run sessions against your live product or prototype and bring back a change list you can use in planning, with clips and the “why” behind each issue. Next, we’ll confirm what you’re testing and build the recruitment and tasks.
We start by agreeing the decisions you need to make, then we recruit the right mix of participants, run a pilot, and move into sessions with tight task wording and consistent note-taking. After each session we log clips to the task, then we turn patterns into specific changes to screens, copy, and steps in the flow.
Who you are working with
We’re a Nairobi-based UX research practice focused on usability research for product teams shipping fast. We built Murram Research around one repeatable rhythm: clear decisions up front, real users completing real tasks, and findings written in the same language the team uses in backlog grooming.
Teams bring us in when analytics and stakeholder opinions point in different directions and the release date stays fixed. We keep the work usable by tying every finding to a step in the flow, showing the clip that supports it, and writing the change as an action a designer or engineer can do on Monday.
The team
You’ll have a small, consistent team on the work, with one lead researcher in every session and ops support keeping recruiting and scheduling moving.
Team
Wanjiku Kamau, Research Director. Wanjiku leads the study design and readout, and keeps the work anchored on the decisions you need for the next sprint.
Brian Otieno, Senior UX Researcher. Brian moderates sessions and pressure-tests tasks, so what we learn maps to the way users actually move through the flow.
Mercy Wairimu, UX Researcher. Mercy runs notes, clip logging, and pattern checks across sessions, so findings don’t hinge on one loud moment.
Kevin Mwangi, Research Ops Lead. Kevin runs research ops: screeners, scheduling, participant comms, and incentives, so sessions start on time and stay filled.
Recent projects
Here are a few recent usability research engagements that ended with concrete changes to onboarding, navigation, and payment steps.
Portfolio
Mobile onboarding usability research. We tested a redesigned sign-up and KYC sequence with moderated sessions, then rewrote tasks and screens around the points where users paused, re-read, or abandoned. The team shipped a shorter path with fewer handoffs between steps.
Checkout and payment flow testing. We ran task-based testing on a payment flow change and traced drop-offs to specific form fields and error states. The result was a set of screen-level edits, copy changes, and validation rules the squad could ticket immediately.
Information architecture card sorting. We used open and closed card sorts to test how people group and label key sections, then validated the new structure with quick tasks. The navigation labels landed closer to the words users reached for without prompting.
“Clear findings, tight clips, and a change list we shipped the same week.”
Product manager, a fast-growing fintech team
Our approach
We keep usability research moving by locking the decisions first, then running a pilot, then sessions with consistent tasks and logging. You’ll see evidence as we go, and you’ll get changes written in backlog-ready language at the end.
1. Plan and recruit Days 1-3 We confirm what you’re testing (live site or prototype), the key decisions, and the target participants. We write the recruitment screener and a sourcing plan. If you have customers you can invite, we’ll use them. If not, we’ll recruit through our panel and partners and manage scheduling and incentives. 2. Script and pilot Day 4 We write the usability test script and task set, then run a pilot session to check task wording, timing, and whether the prototype supports the path. We tighten the script before the main sessions start, so later sessions answer the same questions in the same way. 3. Run sessions and log Days 5-8 We run moderated sessions (remote or in-person), with live note-taking and clip logging tied to each task and step in the flow. After each session we tag breakdowns, workarounds, and decision points. If something needs a quick follow-up task, we adjust between sessions instead of waiting for the end. 4. Readout and change list Days 9-10 We turn patterns into a ranked findings set, with evidence for each item and a clear recommendation written as a change to the flow. We run a readout with your team, answer questions in the room, and agree what goes into the next sprint versus what waits behind the release.
Recruitment screener
A ready-to-send screener with the pass and fail rules, so recruiting stays consistent across participants and you know who we spoke to.
TEST SCRIPT AND TASK SET
A facilitator script and tasks written to your flow, including success criteria for each task and the prompts we use when someone gets stuck.
SESSION RECORDINGS AND CLIP SET
Links to recordings plus a curated set of clips labeled by task and issue, so you can show evidence in planning without rewatching full sessions.
Findings and change list
A ranked set of findings tied to steps in the flow, with the cause we observed and a specific change to make to screens, copy, or logic.
READOUT WORKSHOP
A live readout with Q and A, where we walk through the evidence and agree what the team changes next and what you park until later.
RESEARCH REPOSITORY NOTES
Clean notes and tags you can reuse, so future squads can find what happened on each task without starting from zero.
What it costs
Choose based on how many flows need decisions in the next sprint. Each option includes planning, running sessions, and a readout with a change list.
Priced items
Next steps
If you want to start usability research this sprint, the fastest path is to lock the flow, dates, and recruiting plan today.
1. Sign this proposal to book the work. 2. Pay the 50% booking invoice within 14 days. 3. Share the prototype or live link and any constraints for recruiting, then we begin.
Signature
Fee summary
Payment
To book the work, we invoice 50% when you sign. We invoice the remaining 50% when we hand over the finished work. Each invoice is payable within 14 days of its date.
Timeline. Our standard schedule is 10 working days from kickoff, using the Plan and recruit through Readout and change list stages in this proposal. The clock starts once access and recruitment inputs are in.
What we need from you. Before Day 1, we need the prototype or live link, target user criteria, any must-test tasks, and a point person for sign-offs. Delays here move session dates and the readout.
Recruiting. Recruiting can be through your customer list or through our sourcing plan. If you supply participants, you handle outreach and incentives. If we source participants, incentives and panel fees are billed separately.
Changes to scope
If the number of flows, sessions, or audiences changes, we will write the change in plain terms and share the price and timeline impact before we proceed. We do not treat changes as surprises.
Confidentiality. We keep your materials, data, and recordings confidential and use them only for this project. If we want to reuse anonymised clips or screenshots in our portfolio, we will ask in writing first.
Recording and storage. We record sessions so you can see what participants did and said. We share recordings and clips through an agreed folder or tool, and we keep a backup for a reasonable period in case links expire.
Sign-off and handover. Handover means you receive the agreed artifacts: recruitment screener; test script and task set; session recordings and clip set; findings and change list; readout workshop; research repository notes. At that point, the project is complete.
