<?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[ImpulsoGov Tech &amp; Product Blog - Medium]]></title>
        <description><![CDATA[Get an inside look at how ImpulsoGov’s tech, product and data teams develop and implement innovative solutions that drive meaningful impact in public health. - Medium]]></description>
        <link>https://medium.com/impulsogov-tech-product-blog?source=rss----e92031bc0f14---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>ImpulsoGov Tech &amp;amp; Product Blog - Medium</title>
            <link>https://medium.com/impulsogov-tech-product-blog?source=rss----e92031bc0f14---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:17:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/impulsogov-tech-product-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How We Do UX Research at ImpulsoGov: A Practical Research Guide — part 2]]></title>
            <link>https://medium.com/impulsogov-tech-product-blog/how-we-do-ux-research-at-impulsogov-a-practical-research-guide-part-2-6d0440e1da05?source=rss----e92031bc0f14---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d0440e1da05</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Isabella Matos]]></dc:creator>
            <pubDate>Wed, 23 Jul 2025 15:42:46 GMT</pubDate>
            <atom:updated>2025-07-23T15:42:46.330Z</atom:updated>
            <content:encoded><![CDATA[<h3>How We Do UX Research at ImpulsoGov: A Practical Research Guide — part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XnqOb8DkcbfyCypl5ppUtg.png" /><figcaption>Illustration by Giovani Flores @flowersgiovani</figcaption></figure><p><a href="https://medium.com/impulsogov-tech-product-blog/how-we-do-ux-research-at-impulsogov-a-practical-research-guide-e35c10266ef9">In this second article of the series,</a> I share two key pillars of how we run research here at ImpulsoGov. First, what happens behind the scenes: from selecting participants to scheduling interviews (a bit of <em>ResearchOps</em>). Then, how we consolidate the data, organize the learnings, and turn all of that into something useful for the team. The goal is to share what’s been working for us, with practical tips that can help others going through similar research moments.</p><h3>Behind the scenes: our process for selecting, contacting, and scheduling interviews</h3><p>Once we know who we want to talk to, we move into one of the trickiest parts of the process, but also one that brings real satisfaction when done right: scheduling the interviews.</p><p>It sounds simple: <strong>Choose users / Reach out / Set a time.</strong></p><p>But without some structure in place, it’s easy to get lost in the middle of it all.</p><p>Over time, we’ve developed a solid flow at ImpulsoGov, and we’ve adopted a few tools that help us a lot along the way.</p><h3>Selecting participants</h3><p>The selection process starts with our Metabase dashboard, where we keep a bunch of useful information that helps us identify the right people to talk to. As I mentioned in Part 1, our data team prepares everything so we can easily filter based on:</p><ul><li>Level of engagement with the platform</li><li>Whether they use a specific feature or not</li><li>Location</li><li>Access level (team coordinator, admin, etc.)</li></ul><p>Once we’ve defined the research criteria, we export the table and make a few adjustments in Google Sheets. If your list came from somewhere else, like a screener form, for example, it’s easy to turn the responses into a spreadsheet and move forward with the process.</p><h3>The spreadsheet setup</h3><p>We usually organize the spreadsheet in three main parts:</p><ol><li><strong>Participant details<br></strong>Name, email or phone number, the group they belong to (e.g., <em>Group 1 — Low Frequency</em>), and other relevant info like city or state.</li><li><strong>Personalized message template<br></strong>We create a base message using a few formulas in Sheets. It includes the participant’s name (to make it more personal) and a short intro about the research, sometimes with a scheduling link.</li><li><strong>Contact tracking<br></strong>This section is <strong>crucial</strong>, especially when we’re trying to reach harder-to-engage users (people who don’t use the product much or who have stopped altogether) We track if we’ve already reached out, if they replied, if they said yes, if we’re still in contact, if we scheduled or completed the interview. In these cases, it’s totally normal to message 10 people to get 1 “yes”, and that’s part of the job. The important thing is not to leave those voices out, because they bring valuable insights we’d miss if we only spoke with the most engaged users.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DdjhEwNd3KRQxe4z1e_nlw.png" /><figcaption>Table for illustrative purposes only; all information is fictitious.</figcaption></figure><p>Another important point in this process is <strong>how we contact participants</strong>. We use <strong>WhatsApp Business</strong> as our main channel, and it makes everything a lot easier, especially when more than one person is managing the recruiting/research. It lets us centralize the conversations, organize replies with <strong>tags and shortcuts</strong>, and add credibility with a business profile (name, description, contact info, etc.).</p><h3>Making scheduling easier</h3><p>To avoid the endless back-and-forth of “can you do this time?” / “nope, what about this one?”, we use <strong>Google Calendar appointment slots</strong>. <a href="https://support.google.com/calendar/answer/10729749?hl=en">Here’s a link to Google’s</a> help page if you want to set it up.</p><p>The idea is simple: we define available slots, and participants pick the time that works best for them. It saves time and makes the process smoother for everyone.</p><p>That said, it’s important to know your audience. If you’re working with people who are less comfortable with tech, sometimes good old manual scheduling is still the best way to go.</p><p>Either way, we always follow up with a <strong>confirmation message</strong> after a slot is booked, just to reinforce the day, time, and meeting link.</p><h3>During interviews</h3><p>Whenever possible, we run interviews in pairs. One person leads the conversation with full focus on listening and keeping a friendly, open tone. The other follows the script, takes notes, and stays alert for anything technical (especially during usability tests, when the prototype might bug out).</p><p>I like to bring people from other teams into these interviews, it’s a great way to connect them with real user experiences.</p><p>We also have a <a href="https://www.notion.so/Agreements-and-Interview-Schedule-2334cbca486580f8b61cc14a6ad928de?pvs=21"><strong>quick-start guide</strong></a> with basic interview tips for team members who are not used to joining these sessions.</p><p>We usually use <strong>Google Meet</strong> for the interviews, which makes it easy to record (always with the participant’s consent, of course). Most people are fine with it when we explain it’s for internal use only. Still, depending on the research, it might be worth preparing a short consent form just to formalize things. Another good option is using a tool that transcribes the conversation to make analysis easier later on.</p><h3>Data consolidation</h3><p>This is one of the most intense parts of the process. We often end up with hours of conversation that we need to turn into something clear, concise, and useful for the team.</p><p>Luckily, a few strategies can make this process less overwhelming, and even enjoyable.</p><h3>Before diving into the actual analysis, three things help a lot:</h3><ul><li><strong>Start with a solid research plan and clear questions<br></strong>As I mentioned <a href="https://medium.com/impulsogov-tech-product-blog/how-we-do-ux-research-at-impulsogov-a-practical-research-guide-e35c10266ef9">in Part 1,</a> good research questions work like a compass. They guide what we’re trying to answer during the analysis stage and help us focus on what matters most.</li><li><strong>Have frequent check-ins with the team<br></strong>After each interview, take five minutes to quickly discuss takeaways. What stood out? Did a hypothesis get stronger or weaker? Did an idea for a feature pop up?<br>These quick debriefs are especially helpful in the first few interviews, they act as a test run and help us refine our approach. This is also very useful in usability testing. If something basic isn’t working in the prototype, we can make minor tweaks (that don’t bias the results) to improve flow. One trick: split your sessions into two rounds (talk to five people, make changes if needed, then test with five more)</li><li><strong>Keep a central note repository<br></strong>It’s really helpful to have a shared space to collect interview notes, but also to record hypotheses, patterns, outliers, curiosities, open questions, and even ideas for future research.Think of it as a collective field notebook, something that supports reasoning and gives consistency to your synthesis work.</li></ul><h3>Starting the consolidation</h3><p>Now that the interviews are done, it’s time for what I see as one of the <strong>most underestimated — and hardest — parts</strong>: making sense of everything and turning it into something the team can actually use.</p><p>There are lots of tools that can help. And while I’m writing this, I’m sure a dozen new AI tools are promising to do it all for you. But more than the tools, what matters most is the <strong>thinking behind the process</strong>.</p><p>The steps I usually follow are:</p><ul><li><strong>Review</strong></li><li><strong>Group</strong></li><li><strong>Select</strong></li><li><strong>Weave the story</strong></li></ul><h3>Review</h3><p>Start by looking back at what was done before the fieldwork: the research plan, the CSD matrix (if you created one), and the core research questions. This helps refresh the memory and clarifies <strong>why</strong> the research was done and <strong>what</strong> we were looking for. You’ll start to see <strong>macro-themes</strong> emerge that can guide how to organize the insights.</p><p>Personally, I like to <strong>re-watch all the interviews</strong>. Yes, it takes time. But it really helps you reconnect with the conversations and spot nuances you might’ve missed. If it’s too much, you can speed up the videos, focus on a few key sessions, or use tools that help navigate the content.</p><p>At ImpulsoGov, we upload the interviews to <strong>Dovetail</strong>, which stores and transcribes the recordings (the Portuguese transcription is surprisingly good!). It also lets us highlight quotes and tag them by theme. But you don’t need Dovetail, you can do the same thing with manual notes, spreadsheets, or other systems.</p><p>What matters is that you start <strong>pulling out relevant quotes</strong> and organizing them around your <strong>main themes</strong>.</p><h3>Grouping (and naming themes)</h3><p>How do you decide on these themes? The best place to start is with your <strong>research questions</strong>.</p><p>For example, if you asked:</p><blockquote><em>“Do users prefer using the product on mobile or desktop? Why? When do they use each one?”</em></blockquote><p>… it makes sense to create a category called <strong>Device usage</strong>, for instance.</p><p>And here’s a pro tip: always create a “miscellaneous” category (like <strong>X</strong> or <strong>Other)</strong> to catch interesting things that don’t fit neatly into a specific theme. That way, you won’t lose good stuff just because it didn’t have a home (yet).</p><h3>Selecting and weaving the insights</h3><p>Once everything’s reviewed and grouped, it’s time to <strong>highlight the most meaningful insights</strong>. Look for <strong>recurring patterns</strong>, but don’t ignore the <strong>outliers,</strong> they can reveal nuances that are just as important.</p><p>For example: in the <strong>Device usage</strong> theme, most users might say they prefer using the product on desktop because it’s more accessible and the screen is bigger. But then one person might say they only use it on mobile, because they need quick access during their workday — and they’d only open the computer if they didn’t receive a printed copy from their manager. That contrast adds depth to the analysis.</p><p>Then comes the storytelling: <strong>how are you going to share this?</strong> How will you interpret and communicate the insights so they make sense to others?</p><p>I always make sure to <strong>include real quotes from participants</strong>. It brings the team closer to the user’s voice, adds weight to what we’re saying, and gives more credibility to the findings. When possible, I also mention the participant’s user group (e.g., high frequency, new users) to give context.</p><p>Finally, choose the best format to share the findings: a doc, a slide deck, or whatever works best for your team and moment. I usually organize it like this:</p><ul><li><strong>Context</strong>: quick explanation of how the research started, with a link to the research plan.</li><li><strong>Methodology and sample</strong>: what actually happened (not just what we planned). Maybe we aimed for 10 interviews and got 8. Maybe we targeted new users but ended up talking to someone who had just created a second account.</li><li><strong>Key findings</strong>: main insights organized by theme.</li><li><strong>Other insights</strong>: optional section for relevant findings that don’t fit the main themes (remember the “X” theme? Here’s a good place for it.)</li><li><strong>Conclusions and recommendations</strong>: this is where we connect the dots and link research to product strategy — and where design can really shine. It’s a space of real influence: guiding decisions, suggesting priorities (or de-prioritizing things), and reflecting on the potential impact on users and the business.</li></ul><p>This is how we’ve been doing research at ImpulsoGov, and it’s been working well so far! Of course, every context is different, but I hope this behind-the-scenes look helps you build your own process. I’d love to hear how others do it too, suggestions are always welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d0440e1da05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/impulsogov-tech-product-blog/how-we-do-ux-research-at-impulsogov-a-practical-research-guide-part-2-6d0440e1da05">How We Do UX Research at ImpulsoGov: A Practical Research Guide — part 2</a> was originally published in <a href="https://medium.com/impulsogov-tech-product-blog">ImpulsoGov Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Do UX Research at ImpulsoGov: A Practical Research Guide]]></title>
            <link>https://medium.com/impulsogov-tech-product-blog/how-we-do-ux-research-at-impulsogov-a-practical-research-guide-e35c10266ef9?source=rss----e92031bc0f14---4</link>
            <guid isPermaLink="false">https://medium.com/p/e35c10266ef9</guid>
            <category><![CDATA[ngo]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Isabella Matos]]></dc:creator>
            <pubDate>Wed, 07 May 2025 15:18:55 GMT</pubDate>
            <atom:updated>2025-05-07T15:18:55.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kjQEQWUkAXeq34OLLEZJ6Q.png" /><figcaption>Illustration by Giovani Flores @flowersgiovani</figcaption></figure><p><strong>Creating a research structure is not simple, and each organization or company will have its own ways, limitations, and realities. In this article, I want to share the structure we currently use at ImpulsoGov.</strong></p><p>The goal is to guide anyone who is trying to set up a research process within their organization and is looking for a reference to get started. I’ll walk you through how we structure our process, sharing real examples from research projects we’ve developed in the design team.</p><blockquote><em>💡</em><strong><em> Important: </em></strong><em>the focus here is on more qualitative research involving direct contact with users — such as interviews, moderated usability tests, field studies, journey mapping, and so on. With some adjustments, I believe this material can also be useful in other contexts.</em></blockquote><h4>Before the Research</h4><p>Before starting any research, we usually gather the team to define <strong>why</strong> we are conducting that investigation: why it exists, and what problem or question we want to better understand. To do this, we often use a classic tool: the <strong>CSD Matrix</strong> (Certainties, Suppositions, and Doubts).</p><p>I really like this stage because it helps us bring together everything we already know about the topic: usage data, insights from previous research, feedback from the support team, and more. It’s the moment where we begin to outline the first contours of what we’re trying to explore, and it’s also great for aligning the team’s existing knowledge.</p><h4>Research Plan</h4><p>Once we have more clarity about the problem and what we want to investigate, we move on to building the <strong>research plan</strong>. This document is essential — it’s not just a timeline, but a place to consolidate everything we’re going to do in the research: the whys, the hows, and the with whoms.</p><p>Besides aligning the team’s expectations, it also helps give clarity about the next steps and serves as a living reference throughout the entire process.</p><p>From here on, I’ll walk you through each piece of the plan we usually create, breaking it down into the following sections:</p><ul><li><strong>Context</strong></li><li><strong>Objective</strong></li><li><strong>Research Roadmap</strong></li><li><strong>Research Questions</strong></li><li><strong>Research Method and Participants</strong></li><li><strong>Recruitment</strong></li><li><strong>Interview Script</strong></li><li><strong>Attachments</strong></li></ul><h4>Context</h4><p>Here, we explain where the need for the research came from. It could be based on usage data, team insights, user feedback, or simply because the research is part of a broader product roadmap or service evolution plan.</p><p>No need to overcomplicate it. One or two paragraphs are usually enough.</p><h4>Objective</h4><p>This is where we make it clear what we want to achieve with the research. It can be broader or more specific, depending on the product moment or the focus of the investigation.</p><p>Whenever I get to this part, I remember my undergraduate scientific research days — and something that still helps me a lot is thinking about <strong>verbs that shape the kind of objective we are aiming for</strong>, such as:</p><ul><li><strong>Knowledge:</strong> define, report, point out</li><li><strong>Understanding:</strong> discuss, explain, examine, identify</li><li><strong>Analysis:</strong> analyze, calculate, debate</li><li><strong>Synthesis:</strong> articulate, gather, propose, organize</li><li><strong>Evaluation:</strong> evaluate, rank, select</li><li><strong>Application:</strong> demonstrate, illustrate, apply</li></ul><p>The idea here is to be concise. One or two sentences usually do the trick.</p><p>Here’s an example of an objective we used in a study to <strong>validate a specific stage of the user journey</strong>, based on an early solution sketch:</p><blockquote>Our goal with this research is to <strong>understand how integrating user lists into daily routines affects the active search process</strong>. We want to answer questions that help us design high-impact improvements for people who already use the product frequently.</blockquote><p>And here’s another example, this time from a concept testing study where we explored early-stage ideas:</p><blockquote>The goal of this research is to <strong>evaluate the potential impact of the concepts we developed to address identified opportunities.</strong> We also want to gather insights to help refine (or even discard) these ideas before moving forward with a more robust development process. The idea is to ensure that our efforts are truly addressing real user needs in the best possible way.</blockquote><h4>Research Roadmap</h4><p>This is probably one of the trickiest parts to put together, but also one of the most important — especially when we need to align expectations with decision-makers (the famous stakeholders 🛹). Since they are not always close to the day-to-day of the research, having a clear timeline helps show that the process is viable and eases any anxiety about it “taking too long.”</p><p>Interestingly, in our research plan at ImpulsoGov, the roadmap appears <strong>right at the beginning of the document</strong>, even though we usually only build it after defining the research questions, methodology, and the size of the participant group. This was a strategic choice: placing it early on gives a sense of practicality and quick wins from the start. But honestly, it’s not a rule — if it makes more sense to leave it for later, that’s perfectly fine too.</p><p>When it comes to building the roadmap itself, there are a lot of factors to consider: the method we’ll use, how recruitment will be handled, upcoming holidays, parallel demands… Plus, things like the type of users we want to reach, the team’s level of dedication, how experienced the researchers are, and how familiar the company already is with research processes.</p><p><strong>In short: there are many variables at play, and each roadmap will have its own particularities.</strong></p><p>I know that giving an example always runs the risk of sounding a bit too generic, but especially for those who are just starting out, having a rough reference can really help.</p><p>Here’s an example of a <strong>research project that was a high priority for us</strong>, but still had to run in parallel with smaller demands. In this case, we talked to 12 users:</p><ul><li>2–3 days for creating the research plan (including the CSD Matrix)</li><li>3–4 days for writing the interview script</li><li>5–7 days for selecting and recruiting users (this can vary a lot depending on how structured your recruitment process already is — I hope to write more about this in a future article, especially when I get into consolidation and analysis)</li><li>8–12 days for conducting the interviews (depending on the number of users and the recruitment logistics)</li><li>5–7 days for consolidating findings and writing the insights report</li></ul><p>And one important detail: <strong>many of these stages can happen in parallel</strong>. So rather than showing just a linear list like this, it’s better to <strong>build a visual roadmap</strong> that shows overlaps, weekends, holidays, and everything else.</p><p>My work partner, Roberta, is great at this!</p><p>You can build this roadmap using tools like <strong>Notion, FigJam, Miro, Mural, Excel…</strong> whatever makes the most sense for your team. Check the example below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nKWd7oR7Q-IWxu87_J2OWg.png" /></figure><h4>Research Questions</h4><p>When structuring the research questions, we need to think about what we want to uncover — the answers we hope to have by the end of our conversations with users. This stage is deeply connected to the <strong>research objectives</strong>, and it’s also closely linked to what we gathered earlier in the <strong>CSD Matrix</strong>. Many times, it’s from our certainties, assumptions, and doubts that broader questions start to emerge.</p><p>I like to build this part collaboratively, even if it’s just by having someone else on the team review and add input. Getting different perspectives at this point can really help uncover blind spots or new paths we hadn’t considered yet.</p><p>And an important point: <strong>research questions are not the same as the questions we will ask directly during interviews</strong>. They are broader — they help guide what we want to learn from the research, and <strong>they free us from worrying too early about how to phrase things perfectly for users</strong>. In other words, we don’t need to worry here about whether a question is leading or awkward, because the focus is on what we want to understand, not yet on how we’ll ask it (that comes when we build the interview script).</p><p>I usually start with a few <strong>macro-questions</strong>, and then break them down into smaller ones. For example, in a research project where we were <strong>testing an early concept for a new feature</strong>, some of the guiding questions we used were:</p><ul><li>Do people use Impulso Previne during their active search routines? → How exactly? At what moments of the user journey is the tool being used?</li><li>Do they prefer using it on their phone or on a computer? → What does the experience look like across different devices?</li></ul><p>Building strong research questions really helps later on, when it’s time to <strong>consolidate findings</strong>. They also work as a compass during interviews, helping us check if we’re staying on track. And they set the foundation for the next step: writing the interview script.</p><h3>Research Method and Participants</h3><p>This is the part where we explain <strong>how</strong> we plan to answer the research questions and reach our objectives.</p><p>I won’t go into detail here about all the different types of research methodologies — there are already plenty of great resources out there. Since the focus of this article is on <strong>qualitative research with close interaction with users</strong>, what I usually do in this section is describe whether we’ll conduct in-depth interviews, focus groups, moderated usability tests, or whatever method fits the study best.</p><p>I also take this opportunity to clearly and simply state <strong>how many people we plan to talk to</strong>. It usually looks something like this:</p><blockquote>To collect data, we will:<em><br>- </em>Conduct <strong>1 focus group</strong> with process assistants (to map out what they already know based on their support experience)<br>- Conduct <strong>12 in-depth interviews</strong> with Team Coordinators</blockquote><p>Or, in another case:</p><blockquote>To answer our research questions, we will:<br>- <strong>Interview 10Primary Health Care Coordinators</strong> to explore how they currently use filters<br>- <strong>Conduct usability tests</strong> to assess how users interact with the new version of the filter</blockquote><h4>Recruitment</h4><p>In this section, we describe <strong>who we want to talk to</strong> during the research. This depends a lot on what we are trying to learn, but in general, we aim to cover <strong>variables that could influence user responses</strong> and bring in a diversity of perspectives.</p><p>Following the example from the previous section: if we’re testing a new filter, we might divide participants between <strong>those who used the old filter</strong> and <strong>those who have never used any filters</strong>. The way we define these profiles will also depend on the kind of user data we already have available.</p><p>Here are some examples of variables that can help shape recruitment:</p><ul><li>Level of engagement with the tool</li><li>Usage (or not) of specific features</li><li>Geographic location (when relevant to the context)</li><li>Access profile (e.g., administrator, coordinator)</li><li>Scores from satisfaction surveys like CSAT</li><li>And so on…</li></ul><p>If at this point you’re thinking, “but I want to talk to <em>every type of user</em>” — great! Then this is exactly the time to intentionally structure that diversity into your sample.</p><p>A practical example: when we were validating a user journey, we organized participants like this:</p><blockquote><strong>Group 1: Low Frequency Users</strong> (accessed the platform 1 day in the last month)<br><strong>Group 2: Medium Frequency Users</strong> (accessed between 2 and 4 days in the last month)<br><strong>Group 3: High Frequency Users</strong> (accessed more than 4 days in the last month)<br>Besides that, we also made sure to include users from different macro-regions and who had joined the platform in different onboarding cycles.</blockquote><p>Finally, in this section, we usually link to whatever material we are using to manage participant selection — whether it’s a spreadsheet, a dashboard on Metabase, a Notion database, or whatever makes sense for the team. That way, everything stays organized and accessible.</p><h4>Interview Script</h4><p>Now it’s finally time to build the script with the questions we will actually ask users.</p><p>This is where we <strong>translate our research questions</strong> into something lighter and more conversational. The goal is not to read off a list of questions, but to create a space where the conversation can flow naturally — without feeling like an interrogation.</p><p>A good script is one that <strong>helps guide the conversation</strong> without making it rigid. The more comfortable users feel, the less likely they are to just tell you what they think you want to hear — and the more likely they are to share things that really matter.</p><p>For example, if we want to find out whether people are using a particular feature, instead of asking that directly, we can explore their daily routine: how they perform certain tasks, what tools they use, what their workflow looks like. Step by step, we lead the conversation to the points we want to understand.</p><p>I like to build <strong>semi-structured scripts</strong>, with <strong>main topics</strong> and <strong>specific details</strong> I want to dig into for each one.</p><p>Here’s an example of how a research question can be turned into a script question:</p><blockquote><strong>Research questions:<br></strong><em>Do people use Impulso Previne during their active search routines (</em>proactive patient identification in primary care<em>)? How exactly? Should we open up access to other user profiles? At what points in the user journey is the tool used? Do they prefer mobile or desktop? How does usage vary across devices?</em></blockquote><blockquote><strong>Script question:<br></strong><em>What does the active search routine look like in your unit? </em>(base question)<br><em>→ </em>People involved / Frequency / Tools used / Devices</blockquote><p>Depending on the type of participant (whether they are more talkative or more reserved) and the topic, you can dive deeper with follow-up questions, like:</p><blockquote>Could you tell me more about when you prefer to use the tool on your phone?Do you have examples of times when you chose the phone and times when you preferred the computer?</blockquote><p>I also always like to start interviews with a <strong>small icebreaker question</strong>.</p><p>It helps create rapport and “warm up” the conversation. Usually, I pick something related to the product’s context — for example, at Impulso, I often ask coordinators to describe the health unit they work in: how it’s organized, how many teams it has, and so on.</p><p>One last tip: whenever possible, it’s very helpful to <strong>test your script before heading into real interviews</strong>.</p><p>If it’s a usability test, you can invite someone from another team — someone who isn’t too familiar with the product — just to check if the flow of the conversation makes sense.</p><p>And if it’s a more exploratory or context-driven interview, it might be worth <strong>planning a pilot interview</strong> to fine-tune the tone, the order of the questions, or spot anything that’s missing.</p><p>If you want to dive deeper into this topic, I highly recommend this <a href="https://www.mergo.com.br/blog/ux-research/roteiro-de-entrevistas-o-que-perguntar-ou-nao-para-as-pessoas-usuarias/">Mergo article about what (and what not) to ask users</a>. It brings great practical examples and reflections for when you’re crafting or reviewing your script.</p><h4>Attachments</h4><p>I like to use this same document to link or attach any materials that might <strong>add context</strong> for whoever is reading it. Besides helping people better understand the study, these attachments also reinforce the credibility of the process and show the foundations behind our research decisions.</p><p>Some examples of what we usually include:</p><ul><li>Dashboards, analyses, or other data sources (internal or external)</li><li>Previous research related to the topic</li><li>User quotes about the topic (from support interactions or other channels)</li><li>Prototypes, if they were used in the research</li><li>Spreadsheets or lists of participant selection criteria</li></ul><p>When the research is finished, I also like to <strong>link the document with the key findings</strong> — where we summarize the main insights from the study — and, when applicable, a folder with the interview recordings. Keeping everything connected in the same document makes it easy to navigate and revisit later.</p><blockquote><em>And that’s how we, at the ImpulsoGov design team, structure our research plans — documents that guide the process, organize our intentions, and help bring clarity to everyone involved.</em></blockquote><p>I hope this content helps anyone who is trying to create (or rethink) a research process inside their organization.</p><p>Not as a definitive recipe, but as a starting point — something that can be adapted according to each team’s context and challenges.</p><p>If you have other ideas, tricks, or details that you usually include in research plans, I’d love to hear about them.</p><p>I truly believe this kind of structure gets better when it’s built by many hands — and many minds :)</p><p>Oh, and since the focus here was mainly on setting up the research plan, I’ll leave the <strong>part about analyzing and sharing key findings</strong> for a future article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35c10266ef9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/impulsogov-tech-product-blog/how-we-do-ux-research-at-impulsogov-a-practical-research-guide-e35c10266ef9">How We Do UX Research at ImpulsoGov: A Practical Research Guide</a> was originally published in <a href="https://medium.com/impulsogov-tech-product-blog">ImpulsoGov Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we built a custom digital product for a pilot healthcare project]]></title>
            <link>https://medium.com/impulsogov-tech-product-blog/how-we-built-a-custom-digital-product-for-a-pilot-healthcare-project-369e2530e595?source=rss----e92031bc0f14---4</link>
            <guid isPermaLink="false">https://medium.com/p/369e2530e595</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[healthcare-technology]]></category>
            <dc:creator><![CDATA[Murilo Celli]]></dc:creator>
            <pubDate>Wed, 16 Apr 2025 15:49:56 GMT</pubDate>
            <atom:updated>2025-04-16T15:49:56.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jI8l4xkBZVcqadKY9wumLw.png" /></figure><p>ImpulsoGov develops free solutions that help SUS (Brazil’s public healthcare system) professionals deliver timely and effective care to those who need it most — when they need it most — preventing disease and saving lives. While much of this work happens through Impulso Previne, a platform that centralizes analysis and recommendations on key Primary Health Care (PHC) indicators, there’s also room for initiatives designed around specific local needs.</p><p>This article presents one of those tailored initiatives: the development of a custom digital solution for the city of <strong>Recife, Pernambuco</strong>, carried out between August 2023 and October 2024. Read on to learn more about how this product came to life and the impact it had on Recife’s public health teams.</p><h3>The diagnosis: an opportunity to build digital solutions for improving the quality of Primary Health Care patient records</h3><p>In the early discovery phase, we conducted fieldwork with Recife’s family health teams. Given the city’s population of roughly 1.5 million, we initially focused on teams within Health Districts I and IV, which group neighborhoods by region. Through both in-person and remote sessions, we explored operational challenges and uncovered a critical, recurring issue: <strong>data inconsistencies in individual PHC patient records</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KAIzMoPhQg-4mEWrnLcaTg.jpeg" /></figure><p>To understand the problem, consider this: the effectiveness of Brazil’s PHC strategy relies heavily on the quality of individual health records. When those records contain errors, the system suffers — health planning is compromised, essential care is delayed, and even public health funding can be affected. These records include both personal identification and sociodemographic/health information, which is essential for correctly assigning patients to health teams based on where they live.</p><p>The most frequent issues we found were:</p><ul><li>Individuals listed at addresses they do not actually reside at</li><li>Household records missing a designated head of household</li></ul><p>In practice, Community Health Agents (ACSs) are the professionals responsible for collecting and updating these records, as well as making regular household visits. And they’re the ones most directly impacted by the inconsistencies. Imagine this (all too real) scenario:</p><ol><li>A woman with hypertension needs regular in-home monitoring.</li><li>Her records contain address or household inconsistencies.</li><li>As a result, her assigned ACS never sees her listed and doesn’t visit her home.</li><li>Without this care, her health condition may worsen.</li></ol><p>In SUS, <strong>a single data error</strong> can mean the difference between proper care and a missed opportunity to prevent a serious condition.</p><h3>Developing the solution: technology in service of public health</h3><p>Based on our initial diagnosis, we followed a structured approach: considering the numerous possible scenarios of registration inconsistencies, we collected and analyzed their frequency among healthcare teams in Sanitary Districts I and IV, which allowed us to prioritize our initial intervention.</p><p>In the context of Primary Health Care, the city of Recife uses the Citizen’s Electronic Health Record (PEC), a public and free solution provided to municipalities by Brazil’s Ministry of Health. The registration inconsistencies we were dealing with were already being identified internally by PEC itself. So, we explored the system’s business rules for flagging these issues and replicated them within our own solution. This was a crucial step to ensure data accuracy, as it aligned our tool with the exact same criteria used by the Ministry of Health.</p><p>In addition, we connected our tool directly to the city’s health data infrastructure, which processes and transmits updates from healthcare teams on a daily basis. This ensured that our solution consistently operated with up-to-date data.</p><p>To tackle this challenge, we developed a strategy built on two complementary pillars:</p><ol><li><strong>Support Tool for Data Inconsistency Resolution</strong></li><li><strong>Monitoring Dashboard for the Quality of Recife’s Territorial Registry</strong></li></ol><h3>1. Inconsistency Correction Support Tool</h3><p>This tool was designed to support Community Health Workers (ACS) in the process of correcting registration data. By integrating the inconsistency rules from PEC itself, it enables ACS to quickly identify problematic records and follow a structured workflow to address each type of issue.</p><p>Built with a user-centered design approach, the tool emphasizes clarity and ease of use. No extensive training required: ACSs can visually sort inconsistencies by type and severity and are guided step by step through each correction. The tool also flags the most urgent records and explains exactly how to fix them, minimizing errors in the process.</p><p>Another key feature is progress tracking, which enables health managers and team leads to monitor how corrections are progressing in real time. This made the data cleanup process significantly more efficient — freeing up health teams to focus on other core PHC tasks.</p><h3>2. PHC Registration Quality Monitoring Dashboard</h3><p>While the correction tool supports daily operations, the dashboard was built to serve health managers with a strategic overview of registration quality.</p><p>It aggregates inconsistency data across health teams and units, making it easy to spot trends, identify areas in need of more support, and measure progress over time. Through visualizations and performance indicators, managers can track which teams are performing best and how corrections are impacting overall data quality.</p><p>The dashboard also supports <strong>cross-team comparisons</strong>, enabling better resource allocation and localized intervention strategies. This level of visibility and control makes decision-making more data-driven and ultimately improves the health services citizens receive.</p><h3>Tangible impact on PHC management</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yzMFYwIGNNdDl2daOSH4YA.png" /></figure><p>After 10 months of implementation, the results speak for themselves. Let’s revisit the earlier scenario — where a woman with hypertension was missed due to a record error. With the support of our solution, here’s what changed:</p><ul><li>The chance of a hypertensive patient securing a consultation <strong>doubled</strong></li><li>The chance of receiving an in-home visit <strong>quadrupled</strong></li></ul><p>That’s a huge win. The project not only improved health record quality — it <strong>reengaged frontline teams</strong> in the data correction process and helped <strong>enhance care delivery</strong> across the board.</p><h3>What we learned</h3><p>Our experience in Recife reinforced the value of <strong>well-designed digital tools</strong> for public health management. By simplifying and scaling the efforts of health professionals, we directly contribute to better PHC delivery and improved outcomes for the population.</p><p>At ImpulsoGov, we believe that strong digital products are built at the intersection of <strong>technology, strategy, and social impact</strong>. We’re committed to refining our platforms to help Brazilian municipalities strengthen their healthcare systems and ensure every citizen has access to more efficient, human-centered care.</p><p>To that end, when this project ended, we formally handed over both the technology and knowledge to the city of Recife. Our goal is to ensure that the improvements are sustainable and that the local government can continue to build on this work, but that’s a story for another article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bS_rs_ex36aaYHF9Bs7yEw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=369e2530e595" width="1" height="1" alt=""><hr><p><a href="https://medium.com/impulsogov-tech-product-blog/how-we-built-a-custom-digital-product-for-a-pilot-healthcare-project-369e2530e595">How we built a custom digital product for a pilot healthcare project</a> was originally published in <a href="https://medium.com/impulsogov-tech-product-blog">ImpulsoGov Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Design in Team Alignment and Co-Creation of Solutions]]></title>
            <link>https://medium.com/impulsogov-tech-product-blog/the-power-of-design-in-team-alignment-and-co-creation-of-solutions-fb114058fc46?source=rss----e92031bc0f14---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb114058fc46</guid>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ngo]]></category>
            <category><![CDATA[blueprint-for-success]]></category>
            <dc:creator><![CDATA[Isabella Matos]]></dc:creator>
            <pubDate>Fri, 24 Jan 2025 14:09:59 GMT</pubDate>
            <atom:updated>2025-01-24T14:09:59.271Z</atom:updated>
            <content:encoded><![CDATA[<p>Organizations growing, changes happening everywhere, and teams increasingly focused on their specific areas — does this sound familiar? This scenario is very common and often leads to a <strong>fragmented view, making it hard to understand how each part connects to the whole.</strong> More importantly, it distances people from how users actually experience a service end-to-end. At ImpulsoGov, we’ve also faced this challenge and have relied on the power of Design to foster a shared vision among teams by providing tools that facilitate conversations and ensure everyone is on the same page.</p><p>Since the beginning of last year, we have been mapping user journeys, which has allowed us to identify vulnerabilities and opportunities while also <strong>bringing other teams closer to the user perspective</strong>. This work has been essential for aligning languages and visions, promoting a holistic understanding of our solution. From these journeys, we recognized the need to consolidate a vision that also embraced our internal processes, realizing that <strong>a service blueprint</strong> could provide this integrated perspective.</p><p>A blueprint maps the relationships between various service components: people, processes, and artifacts (whether physical or digital) that are directly <strong>connected to touchpoints within a specific customer journey.</strong></p><h3>Creating a Blueprint: Gathering and Organizing Information</h3><ul><li><strong>Choosing a User Perspective</strong></li></ul><p>At ImpulsoGov, a nonprofit organization offering free support to municipalities for public health management, we have launched various projects. For the development of our blueprint, we chose to work with Impulso Previne, a project that centralizes data, analysis, and recommendations related to Primary Health Care (PHC) financing programs into a single digital platform. The primary users of this solution are PHC Coordinators and PHC team Coordinators.</p><p>Considering that PHC Coordinators are users who interact with Impulso Previne during the early stages of our service, we decided to adopt their perspective as the foundation for structuring the mapping.</p><ul><li><strong>Creating the first draft from internal materials</strong></li></ul><p>To put together the first draft of our service blueprint, we started with the journey of Primary Health Care (PHC) Coordinators, which had already been mapped out and validated through user research. We also <strong>brought in internal resources</strong> like past research, flowcharts, user funnels, and data dashboards</p><ul><li><strong>Collaborating with Teams to Connect the Dots and Gather Artifacts</strong></li></ul><p>With the initial draft in hand, we began <strong>engaging with the various teams involved in operations</strong> at different levels. We spoke with individuals responsible for:</p><ul><li>Conducting outreach and managing communication strategies to promote the tool.</li><li>Designing and delivering onboarding presentations and training sessions for municipal users.</li><li>Providing ongoing user support through WhatsApp, handling everything from registration to technical assistance.</li><li>Managing the end-to-end process of selecting and establishing partnerships with new municipalities.</li></ul><p>These discussions allowed us to refine and improve the stages of our mapping while gathering artifacts used during user interactions, such as WhatsApp conversation screenshots, email templates, Instagram content, event invitations, and more. This phase also <strong>deepened our understanding of each team’s contributions,</strong> clarified the stages where various municipal actors are involved, and revealed the extensive behind-the-scenes efforts required to deliver the user experience we currently provide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hms70P0un6tWcERqnRw2iQ.png" /></figure><h3>Bringing the Blueprint to Life: Aligning Teams and Sparking Collaboration</h3><p>With the second version of the blueprint completed, it was time to share the results with the entire team. We took advantage of one of our in-person biannual meetings, which we call “Immersion,” to showcase the blueprint to everyone. We printed large plots of the stages and stuck them on the wall, creating a giant organized mess. Over two days of immersion, people wandered by, curiously reading parts of the blueprint and making comments with each other. This interaction set the stage for the dynamic workshop we held on the third day.</p><p>We started by giving all teams time to review the information, go through the stages, and examine the details of the artifacts collected. To improve the understanding, we also brought two validated user journeys: the PHC Team Coordinator and the PHC Coordinator. While browsing the blueprint, participants were equipped with sticky notes to jot down observations. Comments like, “We could shorten this form,” “What if we changed the team responsible for this step to make better use of resources?” and “I didn’t know this stage worked like this!” naturally emerged as they uncovered <strong>details they hadn’t noticed before.</strong></p><p>The workshop continued with participants divided into groups made up of members from different teams (health specialists, product and operations managers, communication, data, etc.). Each group discussed critical points of the blueprint, ranked their top three, and brainstormed solutions, eventually sharing their ideas in quick presentations to the other groups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mo1Za4TxSBqja_DBYvkBBQ.png" /></figure><h3>Beyond the Workshop: The Blueprint in Our Daily Life</h3><p>The conclusion of the workshop and immersion resulted in much more than just a blueprint;<strong> it became a living reference, frequently revisited in strategic and operational discussions.</strong> This tool not only highlighted areas for improvement but also played a crucial role in aligning the team and strengthening empathy among its members. The process clearly demonstrated the power of human-centered service design, which considers both users and the internal team.</p><p>In daily operations, the blueprint has proven to be an invaluable ally in several ways. It helps identify bottlenecks and inefficiencies, enabling the team to make more informed decisions and continuously improve services. When onboarding new employees, the blueprint simplifies the integration process, offering a clear and contextualized view of the organization’s operations. Additionally, it ensures alignment between teams, helping everyone understand their role in the user journey and the impact of their actions. Moreover, it serves as a powerful tool for developing new services, uncovering opportunities to better meet user needs. In all these applications, the blueprint reaffirms its value as an essential guide for <strong>delivering a more efficient and human-centered service experience.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8Yz7DwodaIdF5ApmngGjg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb114058fc46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/impulsogov-tech-product-blog/the-power-of-design-in-team-alignment-and-co-creation-of-solutions-fb114058fc46">The Power of Design in Team Alignment and Co-Creation of Solutions</a> was originally published in <a href="https://medium.com/impulsogov-tech-product-blog">ImpulsoGov Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Town Computers to the Dashboard: How We Generate Data Intelligence for Our Partner…]]></title>
            <link>https://medium.com/impulsogov-tech-product-blog/from-town-computers-to-the-dashboard-how-we-generate-data-intelligence-for-our-partner-d44745a8c948?source=rss----e92031bc0f14---4</link>
            <guid isPermaLink="false">https://medium.com/p/d44745a8c948</guid>
            <category><![CDATA[public-health]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Alexsandro dos Santos]]></dc:creator>
            <pubDate>Mon, 02 Dec 2024 13:39:34 GMT</pubDate>
            <atom:updated>2024-12-02T13:39:34.809Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Town Computers to the Dashboard: How We Generate Data Intelligence for Our Partner Municipalities</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XxiJKjQwnvtpgUnqYY47uw.png" /><figcaption>Impulso Previne&#39;s Nominal List</figcaption></figure><p>Impulso Previne transforms raw data into valuable tools for primary healthcare in Brazil. But how do we achieve this? <strong>How does a mass of numbers and tables become actionable intelligence for our municipalities?</strong> In this text, I’ll take you behind the scenes of this process — let’s dive in!</p><p>Impulso Previne was created to address a critical need: helping frontline healthcare professionals — such as nurses and community health agents — prioritize their actions, improve care, and achieve key public health goals.</p><p>Working with these indicators is essential to guide efforts toward a healthier population.</p><p><strong>Among our key deliverables are the Nominal Lists</strong>: a feature that shows healthcare professionals which citizens have pending appointments or exams related to seven health indicators. This approach facilitates planning and action for professionals, ensuring more effective results for municipalities.</p><h3>Refining the Nominal List</h3><p>Nominal lists are essentially tables where each row represents the denominator of an indicator, outlining the criteria that need to be met for that row to appear in the numerator. For instance, an indicator might be as simple as listing all pregnant women in the municipality versus those up-to-date with exams. However, complexity grows when we want to include all prenatal visits, syphilis and HIV tests, and other relevant factors for professionals to monitor in an integrated way. To calculate this indicator, <strong>we rely on a team of public health specialists at ImpulsoGov who work alongside data engineers and analysts to collaboratively build these business rules.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*S8b1bgvnUrfcKt-X_ebgQw.png" /><figcaption>Three different type of professionals are the core to a good Nominal List and understand of the metrics</figcaption></figure><p>At this stage, we also involve a third agent: SUS itself. Often, during the development of a nominal list, questions arise about the text or interpretation of technical notes. To resolve these, we submit requests through the Access to Information Law (LAI), ensuring greater accuracy and compliance in understanding the rules.</p><p>After several iterations and improvements in the indicator calculation’s confidence and the nominal list’s structure, it’s time to operationalize. For this, <strong>we rely on data ingestion and transformation steps developed by our data engineers.</strong></p><h3>From Municipality to the Data Lake</h3><p>At ImpulsoGov, we’ve built an independent application called “Transmissor.” This transmitter is installed on the computers of partner municipalities and sends locally generated information, such as exams, vaccinations, or any other relevant events for the previous calculation steps, to ImpulsoGov’s cloud daily. This step requires special attention, as we not only adhere to the LGPD (Brazilian General Data Protection Law) but also prioritize the security of data transmission and storage.</p><p>This integration is only possible thanks to the PEC E-SUS, an application used to nationally integrate data generated by all primary healthcare units in the municipality. It gathers information such as administered vaccines, performed procedures, and home visits, ensuring all these records are centralized in one place. This centralization, enabled by PEC, is crucial for ImpulsoGov to transform fragmented data into actionable intelligence — something that would be impractical if each professional stored data separately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XXMUxyTwWy9bzo_quqYLA.jpeg" /></figure><p>With data centralized in PEC, our transmitter captures relevant information and forwards it to our cloud-based data platform. There, it undergoes a <strong>three-step process</strong>: first, the data is stored in the “<strong>bronze layer</strong>,” where we receive raw information; next, it moves to the “<strong>silver layer</strong>,” where we evaluate and organize the essential data to ensure its quality; finally, it reaches the “<strong>gold layer</strong>,” where the data is ready to be used by internal or external applications we offer.</p><p>In summary:</p><p><em>Bronze Layer:</em></p><ul><li>Receives PEC E-SUS data from municipalities.</li></ul><p><em>Silver Layer:</em></p><ul><li>Cleans and enriches data.</li><li>Organizes important data.</li></ul><p><em>Gold Layer:</em></p><ul><li>Data already aggregated into indicators.</li><li>Ready-to-use nominal lists.</li></ul><p>These processed data are used by different ImpulsoGov teams to monitor municipalities’ performance, such as data analysts, impact assessment specialists, and public health specialists. However, there’s still one more step: delivering this information directly to municipal healthcare professionals, where it creates the most value. And that’s what we’ll talk about in the next section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*o_rTTl9HJHcTr1TvIBVoMA.jpeg" /><figcaption>Impulso Previne simplified Data Lake structure</figcaption></figure><h3>From the Data Lake to the Dashboard</h3><p>We understand that healthcare professionals’ attention is valuable. Every minute spent trying to understand a tool could mean less time dedicated to citizen care. That’s why our nominal lists must be <strong>intuitive, useful, and comprehensive</strong>.</p><p>During the earlier stages of list construction, the focus is on bringing columns related to indicator calculations. However, this information alone is often insufficient. Only frontline healthcare professionals truly understand the importance of, for example, sorting a nominal list of hypertensive patients by age to prioritize care or including a column indicating the last time a citizen was attended to and by whom. To meet these demands, our tables go through an enrichment phase, incorporating contributions not only from end users but also from the product team and feedback from ImpulsoGov designers.</p><p>At the end of all these stages, we have prepared tables delivered to the frontline professionals, but the work doesn’t stop there. We continue to receive constant feedback to address possible flaws in data transformations. Health data is complex, and specific cases can sometimes go unnoticed. Our ongoing effort is to identify new information that may be relevant to users’ daily activities, striking a balance between providing valuable data and avoiding overloading the interface with unnecessary information.</p><p>Thus, our dashboards do more than inform — they transform how healthcare professionals act, optimizing processes and improving outcomes. In this way, we remain committed to continuously improving our solutions, always focusing on positive impacts for public health.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d44745a8c948" width="1" height="1" alt=""><hr><p><a href="https://medium.com/impulsogov-tech-product-blog/from-town-computers-to-the-dashboard-how-we-generate-data-intelligence-for-our-partner-d44745a8c948">From Town Computers to the Dashboard: How We Generate Data Intelligence for Our Partner…</a> was originally published in <a href="https://medium.com/impulsogov-tech-product-blog">ImpulsoGov Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Strategy for Nonprofits: A Foreword]]></title>
            <link>https://medium.com/impulsogov-tech-product-blog/product-strategy-for-nonprofits-a-foreword-8ea3eb7787f4?source=rss----e92031bc0f14---4</link>
            <guid isPermaLink="false">https://medium.com/p/8ea3eb7787f4</guid>
            <category><![CDATA[nonprofit-marketing]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[nonprofit-technology]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[nonprofit]]></category>
            <dc:creator><![CDATA[Gil Santanna]]></dc:creator>
            <pubDate>Wed, 23 Oct 2024 13:55:48 GMT</pubDate>
            <atom:updated>2024-10-23T13:55:48.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6D2DlvVMRRJK0L5ZtTABg.png" /></figure><p>Nonprofits are vital engines of social change, yet they often lack the tools and frameworks needed to build impactful, scalable, and sustainable products. In the tech world, product strategy has been dissected, refined, and shared endlessly — for startups, big tech, consumer brands, and more — <strong>but the same cannot be said for the nonprofit space</strong>.</p><p>We want to change that.</p><p>After years of experience in the private sector building companies and data products, I have recently turned my focus to the nonprofit sector, I’ve seen firsthand how nonprofits struggle with creating a clear product strategy. Nonprofits are unique; they operate with the vision of maximizing social impact while often being constrained by limited resources, complex stakeholder relationships, and a challenging funding environment. Crafting a product strategy for these organizations requires more than just adapting frameworks from the corporate world — <strong>it needs an approach tailored to their specific mission-driven context</strong>.</p><p>This article is the beginning of a series dedicated to demystifying product strategy for nonprofits. We aim to contribute as a reference point in the discussion on this topic, not because we have all the answers, but because we understand the nuances of this space and are committed to sharing the learnings that can guide social organizations toward creating truly impactful products.</p><p>At <a href="https://www.impulsogov.org/">ImpulsoGov</a>, we create simple and scalable prevention solutions for the public health sector, with a multidisciplinary team of over 50 professionals experienced in big techs and leading technology companies, healthcare, and government.</p><h3>Why Product Strategy Matters for Nonprofits</h3><p>Early in my journey in the nonprofit sector, I learned that many organizations were struggling to innovate and build resilient products that deliver value over time. Most nonprofits are skilled in operations and are filled with passionate people doing impactful work on the ground —<strong> they are too good on PROJECT management</strong>. However, they often lack the tools, frameworks, and focus needed to craft a vision for the future of their products. This is where strategic thinking — the kind that’s grounded in understanding the mission and effectively utilizing limited resources — can make a real difference.</p><p>In tech and corporate environments, a good product strategy acts as a north star, guiding decision-making, aligning stakeholders, and enabling organizations to navigate complexity and uncertainty.<strong> For nonprofits, product strategy can do the same — with one key difference: the goal isn’t profit maximization but impact maximization. </strong>By framing product strategy in terms of how we increase our societal impact, we can develop focused, enduring solutions that are hard to copy, easy to sustain, and ultimately fulfill the nonprofit’s mission.</p><h3>What You Can Expect from This Series</h3><p>This series is designed to be a step-by-step guide for nonprofit leaders, product managers, and teams looking to create and refine their product strategies. I’ll be sharing lessons from both successes and failures — drawing from my experience across different roles — and introducing frameworks specifically adapted to the nonprofit context. Here’s what to expect:</p><p><strong>#1 — The Mission-Impact Model (MIM)</strong></p><ul><li><em>How to align your product strategy with your mission and prioritize impact.</em></li></ul><p><strong>#2 — Understanding Your Beneficiaries</strong></p><ul><li><em>Techniques for deep empathy and uncovering the real needs of your beneficiaries.</em></li></ul><p><strong>#3 — From Mission to Product Vision</strong></p><ul><li><em>Translating your mission into a clear product vision and north star.</em></li></ul><p><strong>#4 — The Resource-Constraint Framework</strong></p><ul><li><em>Leveraging limited resources strategically to create the maximum impact.</em></li></ul><p><strong>#5 — The Strategy-Metric-Tactic Approach</strong></p><ul><li><em>Balancing qualitative impact metrics with actionable tactics.</em></li></ul><p><strong>#6 — Stakeholder Management</strong></p><ul><li><em>Aligning diverse stakeholder expectations with the product strategy.</em></li></ul><p><strong>#7 — Product Roadmap for Nonprofits</strong></p><ul><li><em>Defining a roadmap that is adaptive and prioritizes resilience.</em></li></ul><p><strong>#8 — Case Studies</strong></p><ul><li><em>Real-life examples of nonprofits that have successfully built effective product strategies, showcasing both wins and lessons learned.</em></li></ul><p>Each piece will offer actionable insights and templates you can adapt directly to your organization’s needs. Whether you are an experienced leader or just starting out on your product journey, this series aims to provide you with the clarity and tools to build something meaningful.</p><h3>Next Steps</h3><p>This series isn’t just about reading — it’s about creating, adapting, and applying these ideas to the unique mission of your organization. My hope is that these essays can spark conversations, inspire new strategies, and enable nonprofits to push the boundaries of what’s possible with their products.</p><p>Follow the <strong>ImpulsoGov Tech and Product Blog</strong> here on Medium to be notified about our upcoming essay: <strong>The Mission-Impact Model (MIM)</strong>. To learn more about our work, visit us on LinkedIn: <a href="http://www.linkedin.com/company/impulsogov">www.linkedin.com/company/impulsogov</a></p><p>If you want to find me on LinkedIn, send me a message <a href="https://www.linkedin.com/in/gilsantanna/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ea3eb7787f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/impulsogov-tech-product-blog/product-strategy-for-nonprofits-a-foreword-8ea3eb7787f4">Product Strategy for Nonprofits: A Foreword</a> was originally published in <a href="https://medium.com/impulsogov-tech-product-blog">ImpulsoGov Tech &amp; Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>