[{"data":1,"prerenderedAt":24},["ShallowReactive",2],{"site-settings":3,"writing-synthesis-is-a-method":15},{"id":4,"site_name":5,"role_title":6,"nav_role_label":7,"availability_status":8,"availability_detail":9,"contact_email":10,"linkedin_url":11,"resume_url":12,"footer_tagline":13,"footer_copyright":14},1,"Jameella","UX Researcher","User research","Currently unavailable","for new projects — at Boots UK as an Experimentation & Discovery User Researcher.","jameellaleadbitter@gmail.com","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjameella-l-184019138\u002F","https:\u002F\u002Fstorage.googleapis.com\u002Fplayground-bucket-v2.teleporthq.io\u002F13741081-65b9-41a7-a581-2e710693e7f4\u002F81d52a29-08eb-4eed-b2f0-f194a9c8a96b","User researcher — turning behaviour into better products for energy, interiors, health and learning teams.","© 2026 Jameella. All rights reserved.",{"id":16,"title":17,"slug":18,"date":19,"description":20,"theme":21,"body":22,"status":23},2,"Synthesis isn't a meeting. It's a method.","synthesis-is-a-method","2026-07-21","Why the best insights come from a deliberate, messy, sometimes boring process — not from a shared document with everyone's highlights in yellow.","Synthesis","\u003Cp>Synthesis is the part of research everyone agrees is important and almost nobody schedules properly. We book the interviews. We book the testing. And then we assume the insights will arrive, fully formed, in the debrief.\u003C\u002Fp>\n\u003Cp>They don't. They arrive in the hour you didn't book, when you're tired and the data is still in three different places.\u003C\u002Fp>\n\u003Ch2>What \"doing synthesis properly\" means to me now\u003C\u002Fh2>\n\u003Cp>It's not a meeting where everyone reads their favourite quotes out loud. It's a working method with the same rigour as the fieldwork:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Individual first, group second.\u003C\u002Fstrong> Everyone who was in the sessions writes their own observations down before anyone shares. Otherwise the loudest researcher sets the frame and the quietest findings never surface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Affinity in the open.\u003C\u002Fstrong> Stickies on a wall — physical or digital — where every quote has to earn its place under a theme. If a quote doesn't fit, the theme is wrong, not the quote.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Disagree out loud.\u003C\u002Fstrong> When two sessions point in opposite directions, that's not noise to average out. It's a finding about segmentation, or about context, and it deserves its own discussion.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stop at insight, not summary.\u003C\u002Fstrong> A theme called \"trust\" is a summary. \"Users distrust the company because error messages read like legal disclaimers, so they call instead of retrying\" is an insight. The second one changes designs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>The awkward truth\u003C\u002Fh2>\n\u003Cp>Synthesis is where the mess shows up — the recruitment problem, the session that went sideways, the theme that only clicked at the end of the process. Keeping the mess visible is the point. When synthesis feels tidy too early, it's usually because someone has decided the answer and is arranging evidence around it.\u003C\u002Fp>","published",1788907169835]