<?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 Public Good Studio on Medium]]></title>
        <description><![CDATA[Stories by Public Good Studio on Medium]]></description>
        <link>https://medium.com/@publicgood-studio?source=rss-9e696df7f8c6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xJ6auctE1vmx4HMgDmuCXQ.png</url>
            <title>Stories by Public Good Studio on Medium</title>
            <link>https://medium.com/@publicgood-studio?source=rss-9e696df7f8c6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:04:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@publicgood-studio/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[Studio Update #2 and How to Plan Pretty Much Anything]]></title>
            <link>https://publicgood-studio.medium.com/studio-update-3-and-how-to-plan-pretty-much-anything-ac5c32fc98ae?source=rss-9e696df7f8c6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac5c32fc98ae</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategic-planning]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Public Good Studio]]></dc:creator>
            <pubDate>Wed, 07 Feb 2024 12:47:23 GMT</pubDate>
            <atom:updated>2024-02-08T12:35:19.440Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>The core theme for the coming months at PGS is going to be focus</em></strong>. We’re working on new client projects, all of which are pretty interesting, including a UX audit for a digital literacy platform and creating software to monitor greenhouse gases for large industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*3Co3tHo30NT7EfjdOUp-7g.png" /></figure><p>A significant part of the work ahead of us this year, however, will be working on our own products. We were very lucky to be awarded a US$75,000 grant by CARIRI and the European Union to build <strong><em>Intrapay</em></strong>: a solution to a long-standing problem with intra-regional payments and export trade: high fees, poor transparency transparency, and predatory pricing.</p><p><strong>We’ve also been making changes with Unqueue</strong>, our software suite, which was initially designed in 2020 to support small businesses but now has applications ranging from medium and large size businesses to governments, all while still supporting a network of micro-entrepreneurs with free delivery payments on inventory and order management. <em>More about that soon.</em></p><p>Unqueue’s biggest potential was always been as a deep infrastructure solution. A testament to this is our most recent awarding by the United Nations Capital Development Fund of a US$100,000 grant to develop a wholesale implementation of the Unqueue infrastructure used to help governments, connect, farmers and buyers both domestically and internationally to reduce middleman fees, and ultimately food costs to the consumer in the Caribbean.</p><p>Since Unqueue’s 2020 launch, this is the first year that feels very <em>planned</em>. The wording is important: it’s also the first year that it’s felt like the plan was something bigger than “<em>stay open, don’t die</em>”. A lot of the work ahead of us is the result of conversations had and plans put in place over a year ago. This planning work has not just been about crafting the future for Unqueue, the Studio, and the services that we want to provide, but also in clarifying the future we want for our team, the company’s purpose, and how we see leadership evolving over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQSCENn-HUijqeLTNmKQ6g.png" /><figcaption>🤔🤔🤔🤔</figcaption></figure><p><strong>The only reason that we’ve been able to focus in this kind of way is because we’ve been accountable to our progress since the start.</strong> Being able to refer to our past and compare it to our present with our future in mind has been an essential skill for planning a tech company that is growing not just in a burgeoning market, but also dealing with being service based, bootstrapped, and potentially unprofitable impact-focused.</p><p>It’s not a difficult process either: most planning takes place with a clear, declaration of intention and tracing them back to actions, measurable outcomes, and clear routes of accountability. The team that’s the best able to outline strategic visions, while also evolving them and staying true to their original intentions, will be the team that sees their efforts realised with quicker and efficiency, essential agility in our market.</p><p>At PGS, my job is to draft the outlines for strategic planning and have them passed by the team so that we can have coordination and sign off to work together. Doing this has gotten a lot easier over time, but here are a few of my tips to make it as efficient as possible:</p><ol><li><strong>Make S.M.A.R.T. goals.</strong> Without bogging us down with jargon, there’s a way in wish you can set goals that can either help you meet your goals or send you crazy. Do some <a href="https://www.atlassian.com/blog/productivity/how-to-write-smart-goals#:~:text=What%20are%20SMART%20goals%3F,within%20a%20certain%20time%20frame.">reading up</a>, and figure out how to set yours.</li><li><strong>Make it about money.</strong> If the goal is related to revenue, it’s a good idea to remind yourself of that, especially if this revenue is critical for survival.</li><li><strong>Pick a person.</strong> Goals don’t get executed by companies, they get executed by people. Ownership of a particular deliverable a goal on a team is essential, and it doesn’t have to be that the team leader is responsible for everything—indeed, it may be the least efficient if they are.</li><li><strong>Give it room. </strong>In my experience, it’s best to outline goals from two perspectives: one an ideal, pie-in-the-sky scenario, and another one when nothing goes right, the enemies have surrounded, and the rations have all run out. Planning for success with both the scenarios in mind allows us to have both an expectation of how bad and good things can get, but also allows us to set our personal expectations around where we should be landing to do either a good job or great job, depending on how important the task is and the resources we have available.</li></ol><p>This approach to strategic planning works for all kinds of things, not just planning projects and companies, but it’s especially efficient for these. At the risk of sounding more organised than I am, there’s a way in which resolving your companies vision to single spreadsheet can be both terrifying and very comforting, depending on what you leave room for.</p><p><strong>You can use </strong><a href="https://docs.google.com/spreadsheets/d/1dhz4gyGvOTLOkoGvyQFIv2eqVFSVRCATk3GSifKjSK4/edit?usp=sharing"><strong>this sample linked here</strong></a> for a copy of the strategic planning template that we use for our company and project planning. Hope it’s helpful!</p><p>—Agyei</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac5c32fc98ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity: Why now?]]></title>
            <link>https://publicgood-studio.medium.com/cybersecurity-why-now-cd5752af46b2?source=rss-9e696df7f8c6------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd5752af46b2</guid>
            <category><![CDATA[strategic-management]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Public Good Studio]]></dc:creator>
            <pubDate>Tue, 14 Nov 2023 22:31:22 GMT</pubDate>
            <atom:updated>2023-11-15T13:08:08.759Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ScTHKWw_cJapGtr-i92ig.png" /></figure><p>What do we want? Pre-built systems! When do we want them? All the time! Or words to that effect. If you want digital solutions, the readymade or white-labeled answers promise ease, speed, and accessibility.</p><p>However, recent cybersecurity breaches, like those affecting Courts and other major players, show how this convenience often comes at a significant cost. The 2019 pandemic transformed our digital habits. It also amplified the risks lurking within these popular systems.</p><p><strong>The problem with baked-in safety</strong></p><p>Pre-built solutions, be they for e-commerce, telecommunications, or general systems infrastructure, offer quick deployment and widespread community support. They’re the off-the-shelf solutions to complex problems. However, the simplicity is superficial; the reality is a labyrinth of risks and vulnerabilities.</p><p>These platforms are akin to well-trodden paths — familiar and so, predictably, more susceptible to exploitation. The widespread adoption of free-to-use platforms like Magento or Wordpress means that sales infrastructure can become prime targets for cybercriminals. The issue is compounded by the fact that many IT administrators, in an effort to escape the complexities of custom solutions, opt for these pre-built systems without fully understanding or addressing their inherent risks.</p><p>The pandemic irrevocably altered the digital landscape. The boxed solution was the only (or most convenient) hope many organizations had — because adaptation is survival — they needed to expand their digital presences. We built Unqueue for e-commerce, and have witnessed a 400% YoY growth in sales since our launch in 2020 — it’s not because we’re the only one; it’s a trend. People are depending more and more on technology. This rapid digitalization, while necessary, has often been executed without a corresponding enhancement in security measures or due process around vital considerations like user experience, usability, and product-market fit.</p><p><strong>Understanding Infrastructure</strong></p><p>The current landscape demands we change how we approach our digital infrastructure. It’s not enough to deploy a system and hope for the best. Organizations need to invest in understanding their infrastructure and how it aligns with their specific operational and customer service needs.</p><p>Take, for example, a major player like Courts in the Caribbean e-commerce sector. Their reliance on a solution like Magento might stem more from a place of convenience or institutional inertia rather than a strategic decision. Considerate risk profiling helps leaders understand the implications, and we’re sure Courts’ leadership would have charted alternative paths if they understood better. PriceSmart uses a combination of Drupal and an AI-powered customer engagement tool called Bloomreach to serve their customers. This may be convenient, but it’s probably also a decision that’s close to the root of their recent cybersecurity problems.</p><p>The problems we’re noticing are not new ones, they are however going to have deeper ramifications as time passes. <strong><em>The main reason: online payments</em></strong>. People are now buying things online, not just storing passport photos and HR records. This changes the incentive of the bad actor, and should influence the decisions of the responsible CTO or IT manager.</p><p>We need to think about building a digital fortress, not just a facade. What we’re talking about here involves a blend of managed infrastructure for complex, high-risk areas and in-house development for aspects directly impacting the customer experience.</p><p>This approach enhances security, ensures a better fit with specific customer needs, and provides greater control over the overall customer experience. From a cybersecurity standpoint, the key is to adopt a proactive, rather than reactive, stance.</p><p>Regular security audits, continuous monitoring, and staying abreast of the latest threats are essential. In terms of cloud architecture, opting for the right managed service can offer robust security protocols, regular updates, and expert monitoring, reducing the risk of breaches.</p><p>In software development, the focus should be on building secure, scalable, and customer-centric solutions. This involves adhering to best practices in coding, investing in thorough testing, and ensuring that security is a foundational aspect of the development process and product scoping, not an afterthought.</p><p>The digital world is evolving, and with it, the nature of cybersecurity threats. For organizations like Courts, TSTT, and others, it’s time to move beyond the comfort zone of pre-built solutions and embrace a more nuanced, infrastructure-first approach. This path is undoubtedly harder, requiring more time, resources, and expertise. However, the payoff in terms of security, customer trust, and long-term sustainability is immeasurable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd5752af46b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we don’t use personas]]></title>
            <link>https://publicgood-studio.medium.com/why-we-dont-use-personas-982b6bf92837?source=rss-9e696df7f8c6------2</link>
            <guid isPermaLink="false">https://medium.com/p/982b6bf92837</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[small-island-states]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Public Good Studio]]></dc:creator>
            <pubDate>Tue, 26 Sep 2023 14:51:21 GMT</pubDate>
            <atom:updated>2023-11-13T19:58:25.015Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Design is a doing word but somewhere on the road to understanding, we lost that sense of momentum.</strong> We got caught up in trade-speak: user experiences, prototypes, customer journey maps.</p><p>Left hanging out there is a big question I’ve become accustomed to answering from tech-conscious CEOs. We’re in the room, we’re talking, but everyone is silently asking, “When are we going to start developing personas?”</p><p>I get it. It feels like the question you came to ask, but the reality is when we’re working together that word is not even going to come up unless it’s in the context of the Maxo Kream tape. Personas may have started their cycle of usefulness as well-intentioned research tools, but quickly became tools for marketing agencies to justify their communications decisions and better distinguish themselves in their desperately competitive environments.</p><p>A persona is a set of assumptions sketched out. The better the designer making the pitch deck, the more convincing, the more believable that drawing will be. The goal is to make data easier to understand, more memorable, and (if we’re lucky) useful to the process of design and communications. This approach should allow potential users or audiences to relate to a real human who embodies the set of characteristics shaded into the persona. This builds empathy for the users so we can more deeply understand their needs. The problem with this is that in 2023, human personal expression is at its peak. There are 22 year olds who knit furiously and 74 year old Twitch streamers.</p><p>When we’re developing tools like a persona, bias injection and demographic dependency is all but inevitable. We are, after all, nothing if not creatures of the information on which we live. No judgement, just a fact. Most persona information is demographic, which is great for producing pie charts and star-ratings, but there ends its usefulness.</p><p>Personas also place a lot of emphasis on unnecessary details, but are often missing something core. Because they’re not grounded in a set of tasks, there’s nothing useful for a designer to actually do (please read <a href="https://medium.com/user-interface-22/when-it-comes-to-personas-the-real-value-is-in-the-scenarios-4405722dd55c">Kim Goodwin’s excellent article</a> about personas and scenarios). Remember, design is a doing word, and usually, personas are for showing, not doing.</p><h3>The Jobs We Do (not the personas we see)</h3><p>As for me and mine, we use <a href="https://jobs-to-be-done.com/what-is-jobs-to-be-done-fea59c8e39eb">Jobs to be Done</a> strategy to develop our user profiles. Instead of staring down the valley of who we think people are, we focus on what they need to achieve. This makes sense to us because this is why we wanted to get to know about them in the first place</p><p>We look at key tasks, outlining both emotional and functional needs that users or customers hope to meet, and develop a set of data that allows us to tie goals to performance indicators and establish differentiation by needs (read: product features or brand attributes).</p><p>The common user archetype is a great example here. If we were to use personas, we’d consider age, location, interests, media consumption, devices, and personality traits. Most of which would be flat assumptions. Using JTBD, we can examine their needs, the metrics they use to check that they’re being met — and the pain points that stand in the way of these goals, whether they be emotional or functional. JTBD gives a basis for the <em>why</em> when we’re making our work, and we use it for every project: branding, product development, ad campaigns, app prototypes. Everything.</p><p>It’s time to stop making products and brand strategies around personas and start by finding out what your targets are trying to accomplish. Because, regardless of background, age, status, and motivation, everybody is trying to get a job done. And, no, it’s often not something you can serve with a ready-made solution, and the investigation takes more time, but it’s worth it. It’s an approach that saves hundreds of thousands of dollars worth of product development time. Too often companies make an app because they think an app should be made.</p><p>A focused JTBD-based UX strategy can help them focus on the reasons they need one (or don’t) and help them tailor its requirements and features to the needs of their target audience, so that they can turn their tech spend into a worthwhile investment.</p><p>—Agyei, PGS CEO</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=982b6bf92837" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Studio update #1]]></title>
            <link>https://publicgood-studio.medium.com/studio-update-1-35cbb8834269?source=rss-9e696df7f8c6------2</link>
            <guid isPermaLink="false">https://medium.com/p/35cbb8834269</guid>
            <category><![CDATA[check-in]]></category>
            <dc:creator><![CDATA[Public Good Studio]]></dc:creator>
            <pubDate>Mon, 07 Aug 2023 20:27:24 GMT</pubDate>
            <atom:updated>2023-08-08T13:17:16.862Z</atom:updated>
            <content:encoded><![CDATA[<p>Our first month as PGS has come with a bunch of new kinds of work: we had to change our name (and go through an intensive re-naming process), rethink positioning, figure out which clients we’re saying no to, and rework our financial projections. For the first few months, I think I’d like to focus on sharing some of the learnings from starting up a design studio. It’s something I’ve done at different scales, but PGS is the first studio I’ve worked at that’s focused exclusively on tech interventions aligned with sustainable development goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GL6aSQZpu-yLKbrU0MSPJA.jpeg" /><figcaption>Some of the PGS team</figcaption></figure><p>Here’s things I’ve learned over the past weeks:</p><p>Firstly, <strong>starting a business that’s not profit-first feels weird</strong>. In many ways I can map the ways in which we’ll be sustainable, but it’s strange to intentionally do work that’s targeted to clients that are classically slow-moving, risk-averse, and slow-to-pay. It’s super rewarding though, to be out there, and to pin our colors to the mast of sustainable development for small island developing states, and to be working on doing something about it, for real.</p><p><strong>We’re financially covered for the rest of the year</strong>, and have been lucky to have been actively working on projects since day one when we were still Unqueue Studio. We’re entering a new cohort of impact-focused clients at decent enough budgets to be able to focus on more like them, and to be encouraged to think that things could be sustainable.</p><p><strong>We have office space, but we’re remote-first babies.</strong> Our shared office space at 65 Carlos street, which is beautiful and has easily the best selection of contemporary Caribbean art curation of any co-working space in the country, remains mostly underused. Maybe we’ll switch the usage model to one that’s on-demand, but it’s becoming clear that we may not really need a permanent physical space, at least in the short term. More talks with the team will reveal the way forward, but it doesn’t feel sensible to only barely occupy a space that’s meant to be partly social. Maybe everybody gets a shared working space allowance for those who want to work out but maybe want more flexibility of location? Time will tell.</p><p><strong>Being active on social media (as a company) is hard.</strong> It’s been the hardest thing at the studio so far, and while I’m grateful that the hardest thing hasn’t been new business, it’s certain to be if we don’t make a more concerted effort, so we will for August. I’ll set low expectations, and that’s smart, but meeting them is smarter.</p><p><strong>We have to scale up the team, again. </strong>Because so much of what we’re doing has so many new parts, it’s hard to think of the industry experts I’d want to hire to staff up with — it’s likely they’d come with learnings from a context that may not work for us. When it comes to core staff, we’ve had really good results in training up sharp interns, so we’ll probably move with hiring another cohort for product management, design, and software development. Maybe you’re a good fit, or know someone? Email jobs@publicgood.studio</p><p><strong>We’re growing, again. </strong>We’ve been awarded just about US$150,000 grant funding over the past two months, for Unqueue and another upcoming project. It’s been a real blur but also a validating testament to the value and potential impact of the kind of work we’re doing in and for the Caribbean. It does mean also that we’ll be scaling some of the Unqueue products across the region, and setting up a few new companies. A series of fresh hells await, but so do new opportunities for Unqueue as we address new verticals beyond just eCommerce for small businesses.</p><p><strong>We have a lot to be grateful for. </strong>Starting a new thing is hard, and the feedback (<em>read: scathing critique</em>) and input (<em>read: merciless edits</em>) that I got from the team, our advisors, past and present clients, and prospective partners has culminated in the PGS we’re so proud to share with everyone. You know who you were — you’re the best!</p><p>Anyway, thanks for checking in. I’ll keep these edits going as things gel, maybe for the next two months or so. Upcoming, we have a few case studies and a publication that we’re excited about.</p><p>More soon!</p><p>Agyei, PGS CEO</p><p>info@publicgood.studio</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eXvqUmrbDX9rd_sZDxUVrw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35cbb8834269" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>