<?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 Krystyna Bihun on Medium]]></title>
        <description><![CDATA[Stories by Krystyna Bihun on Medium]]></description>
        <link>https://medium.com/@krystyna.bihun?source=rss-9112e1814880------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DaSqd1ICcCUWgp3bNGToVw.jpeg</url>
            <title>Stories by Krystyna Bihun on Medium</title>
            <link>https://medium.com/@krystyna.bihun?source=rss-9112e1814880------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:45:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@krystyna.bihun/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[Crafting The Financial Archetypes at Neo]]></title>
            <link>https://medium.com/@krystyna.bihun/crafting-the-financial-archetypes-at-neo-f17d58450b9d?source=rss-9112e1814880------2</link>
            <guid isPermaLink="false">https://medium.com/p/f17d58450b9d</guid>
            <category><![CDATA[archetypes]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[canadian-finance]]></category>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Krystyna Bihun]]></dc:creator>
            <pubDate>Thu, 18 Jan 2024 23:07:17 GMT</pubDate>
            <atom:updated>2024-01-18T23:07:17.698Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8umkO8EaGjGZaQFPA6kNYg.png" /></figure><p>One of my proudest accomplishments last year was completing the Financial Archetypes at Neo Financial. It can be difficult as a start-up to know who you are solving for with a fresh identity and super adaptability, especially when your product and services seem to apply to anyone. Almost everybody banks, and almost everybody does at least some of their banking online by now. Banking activities can mean a quick check of your balances before a large purchase or a sit-down analysis on a Saturday morning with a cup of tea, because let’s be serious, sometimes it takes a while to figure out what future you can afford. Women have full control of their money nowadays and some form of banking happens at any age you have money — which does not leave out very many people. We’ve all heard that the product for everyone is the product for no one — so this was no small task.</p><p>The below article includes the following with how I created Neo’s Financial Archetypes.</p><p>Section 1: A Need for Product Design</p><p>Section 2: The Scope</p><p>Section 3: Why we made Archetypes and not Personas</p><p>Section 4: How the Archetypes were made</p><p>Section 5: Do we need to add more Archetypes?</p><p><strong>1. A Need for Product Design</strong></p><p>As Neo grew as a company, we became mature enough to need some guidance, but were young enough that we moved lightning fast, had brand updates on the regular, and were expanding our financial product offerings. The idea of Persona’s was brought up by the Product Design team. They often asked <em>“who are our people, who uses Neo, what do they need, and how does that influence our designs?”.</em> Every good designer should be asking these questions and every researcher would be excited to answer them. There was a need emerging from the Marketing Team as well to better understand our audience, so seeing the opportunity, I decided to take it.</p><p><strong>2. The Scope</strong></p><p>Managing stakeholders for this endeavour was a task in itself. Once a project of this nature begins and other teams hear about it, they want a piece. As mentioned above, there was already a wide net cast for who our audience is, or who we wanted our audience to be — we were still debating this throughout the project. Do we include business terminology and segmentation? Do we include certain criteria that the marketing and communications teams wanted to work with? Did this include all financial products or do we prioritize our credit products because that’s where we have the most customer usage? This opportunity was becoming much more challenging than I expected.</p><p><strong>3. Why we made Archetypes and not Personas</strong></p><p>During the scoping of all these questions, I did what any researcher would do. I looked at examples, shared and got multiple rounds of feedback from different teams to learn what they thought worked and what didn’t. Naturally, I came across some really great resources and articles that helped point me in the right direction. I realized we weren’t making persona’s and I wasn’t going to be able to create a deliverable that would make everyone happy — I had to focus on Product Design and then let other teams internally benefit as a ripple effect but should not distract from my priority.</p><p>This meant cutting out demographics, information, and negativity that helped to generate bias against the deliverable. Criteria such as age, gender, education, even location and names were cut. It should not matter if a young male lived in a small town and makes X amount of money. People use and think about money very differently with that criteria alone. We also didn’t want to give labels such as Sour Sam to describe people. So that information was considered a distraction.</p><p>Because there were some major constraints with gathering big data, and on products we hadn’t launched yet (but wanted to inform), I made another decision to eliminate the idea that we would have perfect data representations based off of stereotypes, such as the fact that people in their middle ages are more likely to buy a home. Who cares? We care if someone is looking for a mortgage and what is most likely to prevent them from becoming a customer with us — regardless of life stage or age. How people look for homes is not quite as predictable as it once was. And if I focussed on these details, I would have 8 persona’s on home buying alone.</p><p>The project was officially referred to as Archetypes since we were not trying to learn about the journey and pains of using a specific product. <strong>What we needed was to understand people’s approaches and attitudes towards their finances.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*09v4oVGS4yQO9ni7bkEYvg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ws0tx1MH516QrESTGnhaOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lxf739fRKULtsAcfDi-JmA.png" /></figure><p><strong>4. How the Archetypes were made</strong></p><p>In-depth interviews were conducted surrounding peoples relationship with their money, knowledge, and association with different financial topics, and opinions on how they would personally change banking for the better. I even got participants to assign an emoji and a rating when they assessed their own knowledge and feelings towards specific topics. There were two groups, which were decided by the Strategy team on peoples financial wellbeing based on income, spending, debt, and assets which was used in a screener. Once divided, they were asked the exact same questions so we could compare.</p><p>The results were a bit surprising to be honest. We expected people who were trending in the direction of building wealth to have similar approaches or relationships with money and vice versa, but that wasn’t necessarily the case.<strong> There were almost no consistent themes with objective markers!</strong></p><p>There were many times during this project that I had to pause but this was a big one. After having to come back after another project, looking back at past research, and then discussing past and recent trends, I realized that our ‘sorting’ wasn’t complete. It wasn’t only about someone’s objective financial standing.</p><blockquote>Instead we were trying to establish a framework wide enough that could apply to any financial product and at the same time be specific enough to help us understand how different people might have different needs when it comes to using digital financial products.</blockquote><p>This would then inform their interests, adoption, usage etc. with financial products and usage on our app.</p><p>Instead, we started referring to groups as having either a Passive or Active involvement or approach to their finances. Much like when I was working on the investing product, these terms were inspired by peoples approaches to how they would prefer to have their investments managed and <strong>how involved they wanted to be.</strong> We saw this again with how people manage their mortgages and how often they checked and paid their credit cards.</p><p>From here, things started to speed up and I was able to split each of those segments one more time to give us four Financial Archetypes, with people’s interest and involvement with their finances being the most differentiating criteria.</p><p><strong>The Unbothered</strong> — Finances are not a current priority where the desire is simply to remove financial barriers</p><p><strong>The Essentialist</strong> — Involved with their finances to a sufficient extent that enables them to support and sustain their desired lifestyle</p><p><strong>The Curious </strong>— Dedicated interest and drive to explore how money and financial products work</p><p><strong>The Architect</strong> — Thoughtfully seeks to understand when and how to optimize finances</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sqil5z1ilLynTE20Hjd5qA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*naFwhJ2TEr3LysRCR_1juA.png" /></figure><p>You can always gather more data and learn more about your users, but when do you know when a project is good enough to be “done”? We arrived at these Archetypes because:</p><ul><li>Once you have a framework for interest and involvement in finances, <strong>you can theoretically apply this to anyone.</strong> These are not focussed on individuals that affords us to narrow our thinking.</li><li><strong>The scale of interest and involvement in finances is a continuous progression.</strong> So even though we have four “buckets”, it is understood that some people might be between some, and that each person does not just sit and stay within one bucket. This means there is also a great opportunity to understand how we can influence people to move between these buckets with marketing and usage etc.</li><li><strong>Since these Archetypes are not specific to a single financial product, you can then apply it to any financial product.</strong> Let me explain; let’s imagine person X has 4 credit cards, invests, and moves money around to take advantage of saving account rates. They could be considered an Architect in each of those financial topics, but might be an Unbothered when it comes to mortgages because they simply don’t need to know about mortgage rates and that whole process. On the flip side, person Y might be The Curious about all kinds of loans (student loans, auto loans) because they have to, but could be The Essentialist with their credit cards if they don’t know about or take advantage of perks and rewards and just use them as a method of payment and nothing more.</li></ul><p>People are complex, and so are their finances. These Archetypes are broad enough to help us learn about most people and most financial products, but at the same time are specific enough to help us understand someone’s approach and needs with a financial topic or product; and then what to change in the digital product.</p><p><strong>5. Do we need to add more Archetypes?</strong></p><p>None of these Archetypes means someone is better off or worse financially than others. It simply helps us understand how to talk to and design for people from a variety of financial circumstances. Every person has a reason for their approach to a certain financial topic or product. When I shared these with the designers I asked the room to think about how the Archetypes related to themselves and even if they could place others they know. We should be happy and proud to identify with any of the Archetypes. If you relate mostly to the Unbothered with budgeting because you have more than enough money for saving and investing for future you, then good for you!</p><p>It’s safe to say the Product Designers and the Content teams were really excited about the Financial Archetypes. Chatter consumed the room and the people present wanted to make quizzes, physical cards, and to share these online. So the question of how we can expand or change the Financial Archetypes eventually came up. We first need to use them enough to gather feedback on how useful or not they are so they could be elevated in the most helpful way possible. But for now, I think they get the job done.</p><p>One consideration however, is the underbanked — a surprisingly larger percentage of Canadians than I think it should be. The typical Underbanked is someone who is new to Canada or is a person with disabilities (of any sort here). We were not able to capture and learn from these groups’ specific needs. I assume their past experiences and unique circumstances would tweak how we sell and onboard them, for example, even if they do generally fit into The Curious or the Unbothered. Then, along with the original four, I think the next steps would be to get more granular with some big data on usage. That will be an exciting time indeed!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f17d58450b9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>