<?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 Kate on Medium]]></title>
        <description><![CDATA[Stories by Kate on Medium]]></description>
        <link>https://medium.com/@katepixels?source=rss-e7a48790536d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4nnF6Vj9kgn8DyfcRx5BJQ.jpeg</url>
            <title>Stories by Kate on Medium</title>
            <link>https://medium.com/@katepixels?source=rss-e7a48790536d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:34:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katepixels/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[ The Anatomy of Innovative Leadership: Five Traits That Set Trailblazers Apart]]></title>
            <link>https://medium.com/@katepixels/the-anatomy-of-innovative-leadership-five-traits-that-set-trailblazers-apart-540d63f1fd57?source=rss-e7a48790536d------2</link>
            <guid isPermaLink="false">https://medium.com/p/540d63f1fd57</guid>
            <dc:creator><![CDATA[Kate]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 21:39:35 GMT</pubDate>
            <atom:updated>2025-08-22T21:39:35.204Z</atom:updated>
            <content:encoded><![CDATA[<p>In an era defined by disruption and reinvention, the leaders who thrive aren’t just adaptive — they’re innovative. They don’t wait for the future to arrive; they actively shape it. But what truly distinguishes innovative leaders from the rest? Beyond frameworks and methodologies, it’s their mindset and lived traits that drive transformation. Here are five defining characteristics that consistently emerge among those who lead with impact and originality.</p><p>1. 🌐 Divergent Experiences: The Power of a Nonlinear Path</p><p>Innovative leaders often draw from a mosaic of experiences — across industries, cultures, and disciplines. These divergent paths cultivate a broader lens for problem-solving and a deeper appreciation for complexity. Rather than relying solely on conventional wisdom, they synthesize insights from unexpected places to spark new ideas.</p><p><strong>Why it matters:</strong><br> A leader who’s worked in both tech startups and public policy, for example, brings a unique blend of agility and governance to strategic decision-making. This cross-pollination fuels innovation by challenging assumptions and expanding possibilities.</p><p>2. 🔍 Curiosity: The Engine of Continuous Discovery</p><p>Curiosity isn’t just a personality trait — it’s a leadership imperative. Innovative leaders ask better questions, explore emerging trends, and remain open to learning from every interaction. Their curiosity drives them to challenge the status quo and uncover hidden opportunities.</p><p><strong>Why it matters:</strong><br> In a world of rapid change, leaders who stay curious are better equipped to anticipate shifts, experiment boldly, and evolve their strategies. Curiosity keeps innovation alive long after the first breakthrough.</p><p>3. 👁️ Keen Observation: Seeing What Others Miss</p><p>While many focus on what’s loud and obvious, innovative leaders excel at noticing the subtle signals — patterns, behaviors, and unmet needs that others overlook. Their observational acuity allows them to identify friction points, emerging risks, and latent potential within systems and teams.</p><p><strong>Why it matters:</strong><br> A leader who observes how teams interact during moments of stress may uncover cultural dynamics that hinder collaboration. By addressing these nuances, they unlock performance and build trust — quietly but powerfully.</p><p>4. ⚡ Challenging the Status Quo: Boldness with Purpose</p><p>Innovative leaders aren’t afraid to question legacy systems, entrenched norms, or “the way things have always been done.” But their challenge is not for disruption’s sake — it’s purposeful. They push boundaries to unlock better outcomes, elevate standards, and drive meaningful progress.</p><p><strong>Why it matters:</strong><br> Whether reimagining customer journeys or redesigning internal workflows, leaders who challenge the status quo create space for reinvention. Their courage inspires others to think differently and act decisively.</p><p>5. 🧠 Pattern Recognition &amp; Synthesis: Connecting the Dots</p><p>At the heart of innovation lies the ability to see what others can’t — emerging trends, hidden relationships, and strategic inflection points. Innovative leaders excel at connecting disparate data, experiences, and signals into coherent insights. They synthesize complexity into clarity.</p><p><strong>Why it matters:</strong><br> A leader who spots a shift in customer sentiment, links it to operational bottlenecks, and translates it into a new service model is practicing innovation in real time. This ability to connect the dots transforms ambiguity into opportunity.</p><p>🚀 Leading Forward</p><p>Innovative leadership isn’t about having the flashiest ideas — it’s about cultivating the traits that enable sustained, meaningful change. Divergent experiences expand perspective. Curiosity fuels exploration. Keen observation reveals the invisible. Challenging the status quo drives transformation. And synthesis turns complexity into strategy. Together, they form the foundation of leadership that not only adapts to the future — but defines it.</p><p>These aren’t just traits — they’re choices.<br>And they shape the kind of leader I strive to be:<br>One who doesn’t just adapt to the future — <br><strong>But defines it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=540d63f1fd57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The power of One.]]></title>
            <link>https://medium.com/@katepixels/the-power-of-one-47d0c6103753?source=rss-e7a48790536d------2</link>
            <guid isPermaLink="false">https://medium.com/p/47d0c6103753</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kate]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 19:14:25 GMT</pubDate>
            <atom:updated>2018-11-28T00:40:04.773Z</atom:updated>
            <content:encoded><![CDATA[<h4>UXDI-13, Project 3: Restrospective</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dfWXwEfhHdAQ0onxlTXkDQ.png" /></figure><p>This was my favorite project to work on. I thoroughly enjoyed having to look at both sides of the equation: the business needs as well as the user needs and doing my best to balance them out with human centric design.</p><p>It was also fun to look behind the scenes, and to understand from industry big wigs — the true motivations behind the app, it’s existence and it’s future roadmap. <em>It’s not everyday that you get to speak to the makers of the app.</em></p><p>But the path to understand how the app had to be redesigned was not always clear-cut, we were often peppered with difficult decisions along the way. Our first difficult decision came on project day 1.</p><h3>The clock is ticking</h3><p>Project 3, Day 1: Our very first task involved deciding on an app to redesign. We were given 24 hours to think over our choice of app. Before the end of the day, my project team mates and I had narrowed it down to three choices.</p><p><strong>iChangi </strong>— the Singapore Changi Airport app portal for flights information, shopping and dining.</p><p><strong>PropertySRX </strong>— A property app used to help people locate property to buy, sell or rent.</p><p><strong>OneService</strong> — a government run application created for residents to quickly report on estate issues and to help route cases efficiently to the respective government agency.</p><p>There was a natural attraction to work on OneService simply because of its premise. Here was an opportunity to redesign an app that was created to help make Singapore a better living place. It felt good to be part of something that would help my fellow countrymen have cleaner estates.</p><p>But hold on a minute, I haven’t heard of this app before!!</p><blockquote>Would I be able to gather sufficient data points, let alone find enough research participants to support my findings? My confidence in choosing this app for redesign was dwindling down and fast.</blockquote><p>My project mates and I discussed in length and decided this is our time to stretch ourselves, to face the unknown and if we make mistakes, we’ll learn along the way. At least, we could still depend on each other for support.</p><h3>Research participants — where are you?</h3><p>Project 3, Day 2: We began by brainstorming and sending out broadcasts to recruit users for our interviews. We stalked the social media sites of OneService, to see which of our friends had liked the OneService facebook page.</p><p>Luckily, in my medicore friendbase of 486 persons, there was one kind soul who was free to be interviewed that very day! (Unfortunately, no photos allowed as he was in uniform).</p><p>From my initial research interview, I had managed to gather feedback on what the app was being used for, what the participant likes or dislikes about the app. The kind soul also did a cognitive walkthrough of the app so that I could observe first hand how the participant interacts with the various features on the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*_efOYIgM5mAJvqy0Pn0enA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/1*ozIgvap7zM2rwu8nz-5Eqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*1w_SRTo0oxX-mzHz6tVM1w.jpeg" /><figcaption>Design and feature limitations on the current app.</figcaption></figure><blockquote>Left screenshot: The horizontal scrolling was not user friendly, especially for those trying to log a case single handedly. This finding was repeated when we tested with older research participants.</blockquote><blockquote>Center screenshot: Research participants did not see usefulness of Location, Parking App and Transaction sections.</blockquote><blockquote>Right screenshot: It was mandatory for the participant to input a picture, when it wasn’t always convenient to do so. Our participant gave the example of noticing potholes along his cycling route, but he wasn’t able to stop and take a picture as he’s in the middle of traffic.</blockquote><p>Here, this affinity map helps to explain it better. Collectively, between my project partners and I, we had interviewed and observed 6 participants (a mix of old and new app users) with age ranges from 28 to 72 years of age.</p><p>Zooming into the dislikes of the users and we could find some main pillars of frustration which could be further broken down into, Lack of purpose, Feedback loop, Reliability, Design and Categorization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5mIyZYZzjSy1wWqlXNLPiQ.png" /></figure><p>a)<strong> Lack of Purpose </strong>— Though the app had well meaning intentions to store all government apps in one place, this didn’t resonate well with research participants who were only looking for a place to lodge complaints and this made the user experience less enjoyable.</p><p>b) <strong>Feedback loop </strong>— users were keen to know that someone is working on their issue, and that they receive regular updates as well as a timeline on when this issue would be resolved. In the current app, it only mentions a few statuses with no estimated timeframes.</p><p>c) <strong>Reliability </strong>— the app was buggy, sometimes the main page would not load. The icons showing the categories were not always showing up, which was not professional.</p><p>d) <strong>Design</strong> — the main page of the app as one participant put it “the dashboard is user unfriendly and confusing” and another had described it as “the transact page is taking up too much space” highlighting the poor space optimization on the page.</p><p>e) <strong>Categorization</strong> — Users were not happy that the app didn’t offer enough flexibility in the categories. Often they would drill down into a sub-category only to be left feeling perplexed “you mean there’s no ‘others’ option?”</p><p>In discussion with my project mates and due to the limited time (2 weeks), we decided to focus our energies on fixing the <strong>Purpose, Categorization</strong> and <strong>Design</strong> issues.</p><h3>Data, data everywhere.</h3><p>Identifying the problem statement was a tough one.</p><p>We combed through our data sets and our participant quotes. There was one recurring theme: participants had questioned the addition of the parking app to OneService and could not relate to the connection between the two services, despite both being government apps.</p><blockquote>“What is this app for? Is it for lodging issues or for parking?”</blockquote><blockquote>“Why does parking have to be added?”</blockquote><blockquote>“Why do I need to go through OneService to get to the parking, when that’s two clicks and I can go to Parking app directly?”</blockquote><p>In line with our affinity mapping results on the lack of purpose, we identified our primary problem statement:</p><h4>Users who use the OneService app to lodge estate-related complaints need to understand the main purpose of the app, so that they are more likely to use the app to make complaints.</h4><p>We also wanted to address the issue of flexibility within the case categorization on the app. On closer inspection of the main categories, we noted the main categories were derived from the key agencies part of OneService. For example “Drinking Water” and “Sewers and Drains” fall within the remit of PUB (Public Utiities Board).</p><p>Through our research interviews, we had asked participants to freely explore the app and lodge a specific scenario such as “noisy coffeeshop”. We noted that many participants had difficulty completing the task as the main categories were a mix of states e.g. “Cleaniness”, places “HDB facilities”, or objects e.g. “Pests”.</p><p>Sometimes when a participant went further into a sub category, they were not provided a subsequent ‘others’ function which caused them to backtrack into the main categories and to reselect their case submission categories again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2N7AG9sntL7b8_VCE9TsqA.png" /></figure><p>Results from our Card Sort and Tree test further validated these points, that the existing app categorizations were not optimized to help reduce the user’s mental load in lodging issues. (e.g. For the case “Cockroaches in food establishments” had 3/11 participants park it under Cleanliness while 3/11 parked it under Pests, the remainder had created their own categories for it as they did not see any main category that fit well.)</p><p>Our secondary problem statement was formed:</p><h4>Users like <strong>having control </strong>over <strong>how and what information</strong> should be included when submitting a case so that they can quickly submit their case.</h4><h3>Understanding the business</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5KcUJNiFZ3e0AJw5uNlEg.jpeg" /></figure><p>Over the course of the next few days, we also looked at the business goals holistically. Through our own connections, we manage to ask the people who worked on the app, their motivations and direction for the app’s future.</p><p>Our business related questions were:</p><ul><li>Why was this app created?</li><li>What are the business objectives of the app?</li><li>How are the cases allocated in the back end?</li><li>What are the future plans for the app?</li></ul><p>Through the responses received, we understood the app was created to remove the resident’s needs to know which agency to approach to resolve a particular estate issue. It also provided a “convenient platform” for residents to lodge issues.</p><p>The future plans of the app was to create a community platform with additional modules or government apps added to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*ufZMdvq7cjes_Q43bF1r9w.png" /><figcaption>NEA, NParks or LTA?</figcaption></figure><p>Through our literature research, we also discovered the “fishball stick issue” which was the catalyst to kickstarting the OneService app. (Fishball stick issue refers to if a fishball stick fell to the ground, which government agency would look after it? Would it be Land Transport Authority, National Parks or National Environment Agency?)</p><h3>The Balancing Act</h3><p>Now that we knew the business motivations and we also had insights from our research participants, we needed a good way to help us identify which features of the app we wanted to keep, remove or evolve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Miic_A7ImFEaVQa3" /></figure><p>We used this prioritization grid and started mapping out existing features (in blue) as well as any new features (in yellow) suggested by participants. Each feature post its were moved around until we could convine ourselves exactly where they sat in the business vs user crosshair.</p><p>We prioritized based on features that will help resolve our two problem statements and made a border on those that would make it into our prototype design.</p><h3>Redesign on the go</h3><p>Armed with our problem statements, business goals and features prioritization we were ready to start paper prototyping! Our three design goals were:</p><ol><li>Make the purpose of the app clear and improve usability for ease of reporting.</li><li>Encourage community interactions, to help raise awareness of the app.</li><li>Reduce the learning curves to make the app accessible to all residents.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/302/1*sKNcpDHJlQ-TdlapVPB7zg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*sbZPAa14ij282B3kGnuBAA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/195/1*TVaBkU-sFiViCWOtSe8xKg.png" /><figcaption>L to R: Home Page, Add Case, More case details</figcaption></figure><p>The home page was redesigned to maximize use of the white space by having each case represented by a card with no more than 4 cards on a single screen.<br>For case submission, the horizontal scroll was also removed and the vertical scroll added.</p><p>When it came to how many main categories or what should be our main categories, we took to the white board. Mustering what I could of my psychology days, I took a look at how a person would instinctively communicate about a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_-a2xJex1DcmcZa8C1_mw.jpeg" /></figure><p>We came up with three high level details that would provide the user sufficient flexibility to permutate and custom their case classification. These categories were also detailed enough to help with the case allocation to the respective agencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*-Y6kWBc5l0S45eba5m1FSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*bpsmcsyE8IxbplKAkPHUhw.png" /></figure><p>1st level — The high level thought of the issue (Animal, Place or Object only e.g. “Animals and Pests”).</p><p>2nd level — A more detailed What of the issue (e.g. “Bees and Hornets”)</p><p>3rd level — The state of the issue, this will have to do with a human being’s senses, it could be a smell, sound or feeling. (e.g. “Nuisance”)</p><p>My project mates and I agreed to workout the new categories and sub categories based on these three levels. At this point, we were pretty much working as One mind (pun intended!).</p><h3>My One, Your One, who is One?</h3><p>Using Figma (a collaborative web based prototyping tool), we converted our paper prototypes into digitized ones. We took our digitized prototypes to test with both the young (think 20s to 30s) and the old (think 50s and above). We quickly came to realize that the the less tech savvy approached screens very differently from those that are more tech savvy.</p><blockquote>a) they were less likely to notice visual cues such as arrows or even guiding prompts (to help them familiarize with lodging a case)<br>b) they did not always know the local slang words like “Gahmen”<br>c) they don’t always recognize the common icons</blockquote><p>These discoveries led us to iterate our design by:</p><blockquote>a) having straight arrows and bigger fonts for guiding prompts<br>b) reducing the amount of slang used among the pages<br>c) labelling all icons.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UowJKJvJspIbDHuwWUL7Aw.png" /></figure><p>In the above design, our goal was to integrate community interactions into the app. Interestingly when we tested with our research participants, Redesign 2 with colored icons was a welcome idea by the tech savvy research participants. In contrast, the less tech savvy participants found it jarring and confusing. The less tech savvy also could not make out the icons or labels as they were too small to see.</p><p>From this feedback, we again reiterated our designs, this time to show cases on cards, there was also a change to map view to retain some of the initial app features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*pkt7oDCoHRDjuMLWJvGNrw.png" /></figure><p>We also didn’t forget our business goals, where the future direction of the app was to include other government apps which transforms it into a one-stop community platform.</p><p>This feature was now neatly tucked away under a Government Apps icon which we have labelled clearly. During the usability testing, one user even mentioned “If there are multiple government apps clustered together, this makes more sense than having a stand alone parking app”.</p><h3>Free Exploration and Usability Testing</h3><p>We had two separate tests run: 1) to validate if the redesign helped to make the purpose of the app clearer and 2) to see if there was improved usability in the design.</p><p>For the first test, we used a free exploration and collected qualitative feedback from our research participants to describe back to us what they thought the purpose of the app was. All participants understood the app to be for lodging issues and the purpose was clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNbjdo0F4RXccx7pEbRXlw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zNJBKTj3s6kkD_Oq90BLg.jpeg" /></figure><p>For our second test, research participants were give three specific scenarios to perform and at the end of the test, each participant provided their satisfaction ratings based on an emoji slider. We had requested for this emoji slider as it was easier for our participants to relate to, they just had to pull the slider till the emoji (frustrated, sad, neutral, happy or elated) matched their own feelings on the matter.</p><p>From the results, I’m happy to know that our redesign achieved our design goals. We had improved both the learning curves and clarity of the purpose of the app from 1.5/5 to 3.5/5. We also simplified the reporting of cases which saw an improvement from 2.5/5 to 4/5.</p><h3>Further iterations</h3><p>Other improvements if time permits, would be to look at language support so support the Mandarin speaking community. We would also look to work with the government’s back end systems to ensure the new categorizations are tagged and in sync with the agency architecture.</p><h3>Takeaways…</h3><p>I definitely have a few takeaways from working on this project.</p><ul><li><strong>Start with your most challenging persona</strong> — if I can solve the usability issues for the most challenging persona, I would be able to solve it for majority of the users.</li><li><strong>Knowing the business needs helps </strong>— sometimes businesses want to achieve a certain outcome. If we can design a product where user goals can help businesses achieve their outcome, it’s a win win situation. The magic is in the design of the product.</li><li><strong>Descoping features is a necessary evil<br></strong>It is very tempting to include every feature your participants tell you to, or even the ones you dream up. But don’t. It’s really important to be discplined and remain focused. Use the results from testing your prototype to form your own guidance on which features won’t make the cut because they don’t add value to the user experience.</li></ul><p>Check out my prototype <a href="https://www.figma.com/proto/u2c2cWevNXiCDASPNeUtmM/Redesign-3?node-id=0%3A1&amp;scaling=scale-down">here</a>.</p><p>Lastly, a big shout out to my project partners Jie Ying and Ethan. Truly a pleasure to work with both of you. Each of you brought their strengths to the table and there was a good push and pull of ideas to get us through the hurdles. You guys rock!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47d0c6103753" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UDXI Project 2 — Retrospective]]></title>
            <link>https://medium.com/@katepixels/udxi-project-2-retrospective-de8ca5ccc0c6?source=rss-e7a48790536d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de8ca5ccc0c6</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kate]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 19:00:26 GMT</pubDate>
            <atom:updated>2018-12-06T06:14:06.840Z</atom:updated>
            <content:encoded><![CDATA[<h3>My school of thought on the school of Art and Design.</h3><p>UDXI — Project 2 Retrospective</p><p>A story about true partnership.</p><p>Our project brief was to redesign an art’s school website, except that this time we would be working with a partner! I was quite excited to have someone to bounce off ideas and to share the workload, rather than having to figure it out all by myself like in Project 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EOXZUs6N5kfO9YvVLEsVLQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XsxZrtR_2DEeG5XeJybZqQ.jpeg" /></figure><p>First off, my partner and I worked on our project log and how to plan our time over the next ten days. Next, we tackled research on the site, by doing some competitive analysis and heuristic evaluations. We collaborated on our discussion guide, and headed down to the school together to conduct our user interviews and our initial card sort test.</p><h3>The first disagreement</h3><p>Day 3 — As we were working through analyzing all of our user responses, my partner suddenly blurted out “I can’t convince myself of what we’re trying to solve.”</p><p>“But isn’t it clear from the responses? What’s there to convince?” I responded quickly, already getting worried about the tasks we were falling behind based on the detailed project log and timeline we had put together on Day 1.</p><p>“No, it’s not clear, I’m going to get more interviews” my partner said as she began to pack her bags. I sunk lower in my chair resigned to her decision, while trying to mask my own frown face.</p><p>It went on like that for the rest of the project. As I was pushing to get us on track for time, my partner was pushing to understand. As I communicated my thoughts on the data analysis, she would question why I thought it was so.</p><blockquote>So it sort of became a habit between the two of us, to always ask each other why (even if we were shared the same opinion as the other).</blockquote><p>We went through our decision points over and over again, we cross validated it against our user research, against our heuristic evaluations, against our site maps, against our designs and against our time line for the project.</p><blockquote>If I had to sum up what we did well, it was that tag team spirit of moving forward to keep our tasks on time, and concurrently diving deeper to analyze our decision points until we could truly convince ourselves.</blockquote><h3>Design Goals</h3><p>After observing our user click around and login for the third time to a third link, just to locate where she would register for classes….I was convinced — these students need a better way to manage their academic matters. As a team, we agreed these would be our design goals:</p><ol><li>An integrated student portal to access school information pertinent to the current student.</li><li>Prioritize the order of information displayed according to the importance of the information to the user.</li><li>Show more of the “WHY” of the school. Be less content heavy, and have more pictures of students creating and designing at school.</li><li>Engage with the users through the terminology used and to keep it consistent.</li></ol><h3>Research and analysis process</h3><p>As part of this project, I also learnt a few new techniques which I will now focus on.</p><p><strong>Heuristic Evaluation and Content Audit</strong></p><p>Doing a content audit for the site was a strangely therapeutic experience, almost like going through the website with a fine toothed comb. In doing so, I discovered some things I probably won’t have noticed if I just continued clicking around the pages. I started to notice repetition within the site.</p><p>Schools, Programs, Degrees, Diplomas, Course Modules were being menitoned repeatedly as I checked through each page. What exactly was the connection here? Soon, I figured out that the school had a couple schools, but these schools ran eight programs in total.</p><blockquote>If we could rearrange how we view the information, it made more sense to go <strong>Programs → Degree/Diploma → Course Description → Course Modules </strong>rather than<br><strong>School → Degree/Diploma → Programs → Course Description → Course Modules.</strong></blockquote><p>Of course, this idea would be validated at a later stage in our Tree test.</p><p><strong>Card Sorting</strong></p><p>Initially we asked our testers to sort through a huge number of cards(43 in total) which comprised of category names that sat at different levels of the navigation hierachy. Even though our results had showed large groups of cards that belonged to each other, it still wasn’t clear enough, as some of groups of cards were overlapping with each other.</p><p>So a second card sort was arranged, but this time we narrowed the scope to only include Primary and Secondary navigation items. We also chose to provide the primary category names and to conduct aclosed sort. This definitely yielded clearer results, with only a couple categories that still had split votes.</p><p><strong>Tree Test</strong></p><p>One of the first tests was to check if going by Programmes → Degree/Diploma would help users locate the course application more easily and it had a 100% success rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*4P-C-r5GyV7htc6ufnGfvA.png" /></figure><p>Another area of focus for my partner and I, were the Tree tests that had high failure rates e.g. Finances at 83% fails, Internship/Attachments at 57% fails and Academic Calendar at 43% fails. This made us scrutinize our site map more closely and we addressed these in the fourth iteration of our Information Architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*BNxucbd22tPo0t3G1kRSdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*jXxR0MWpe4d5AUY6yFMPRg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*LUqFzkjFeLqYOp7aR9O0lA.png" /><figcaption>L to R — Academic Calendar, Internships/Attachments, Finances</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EKIVB01_smBrva--VA08bw.png" /></figure><p>In summary, we made three key changes to our Information Architecture (IA):</p><p><strong>Academic Calendar </strong>was kept both within the student login as well as outside together with the general navigation of the website.</p><p><strong>Internships/Attachments</strong> was renamed as Career Services and moved upfront in the student portal under Student Services</p><p><strong>Finances </strong>was kept as a section on its own within the student login.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XHQkGJNNS6EO5QoPhM_tJA.png" /><figcaption>Our Persona — Evelin (not her real name)</figcaption></figure><h3>Userflows</h3><p>Okay, so now it’s time to validate that our site map meets the needs of our persona.</p><p>But wait, first meet Evelin, the persona we had in mind for this project. We chose to prioritize her needs on registering for electives, downloading lecture notes and handling administrative matters. Through our observations of the students using the current website, they often faced confusion of not remembering where information was kept on the site. On top of that, they had to deal with multiple sites that stored information they would use on a daily basis.</p><p>After repeatedly observing the painful process of retreving information from multiple sites within the school website, this observation alone was compelling enough for both my partner and I to agree this was definitely a pain point we wanted to address.</p><p>Here’s our userflow (before) and (after) the redesign of the IA. With the redesign, the students now had an efficient way to cross over to the various functions that they would via the integrated portal vs the old way of logging out of one system (that handled registration of courses) and logging into another system (that handled finances).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*g78R2TnyQ7IX0gaGrRiN0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*3FT-w7AtRoIHDbdcno4x3w.png" /><figcaption>L-R: Old userflow, New userflow</figcaption></figure><h3>Design and Prototyping</h3><p>Here are some of our initial sketches while we played around with the idea of an integrated portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wffi40s5i7tc4Mx58oz0ag.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6qfVDg_iBJ8ZydwGOEieaA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lVlnBOHnhmGhmI1eVKCWAA.jpeg" /><figcaption>From L-R, hand sketches of our Programs page, Course Description and Career Advise pages</figcaption></figure><p>After our first usability test, we received insightful feedback from the students on the student dashboard. Most liked the idea of an integrated dashboard where they could view all their course, and administrative matters in a one stop shop.</p><p>However, we took their feedback seriously and did a iteration of the page. See below for changes we had made based on the feedback received.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jkits36XSlJYV76bOEVHsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WktVUE2o4zcPzK7LHnx5A.png" /></figure><h3>Learnings</h3><p>Some key learnings from this project that I’ll like to bring along with me for my UX journey are…..</p><ul><li><strong>Leverage on your teammate’s strengths</strong><br>Everyone brings a different skillset to the table, and it may challenge you in ways you never thought possible. Embrace that good tension and work through it as a team.</li><li><strong>Question everything, even if you already believe it</strong><br>It’s a new skill for me to learn, but to convince myself and playing my own devil’s advocate for each decision does not come naturally.</li><li><strong>Keep a diary of your thought process</strong><br>Two week sprints go by really fast, and because you’re processing a lot of changes, it makes it difficult to remember exactly what you were thinking at each stage of the process. Jot them down, it helps.</li></ul><h3>No design is perfect</h3><p>As with all sprints, time is never on our side. If there was more time, I would like to build up more on the notifications function, where many students had mentioned they used the course registration alerts from it to register for courses.</p><p>I would also have liked to do more Tree testing to further refine the main navigation categories — as from the results of our 2nd card sort there were some categories that were still remained ambigious to the users.</p><p>Using heuristic evaluation on the redesign, I think we could have included more help and documentation features around the website.</p><p>With that, I’ve come to the end of my retrospective. I hope you’ve enjoyed reading this as much as I have enjoyed putting it together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de8ca5ccc0c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UXDI Project 1 — Retrospective]]></title>
            <link>https://medium.com/@katepixels/uxdi-project-1-retrospective-a5b809071b5b?source=rss-e7a48790536d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5b809071b5b</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kate]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 15:36:59 GMT</pubDate>
            <atom:updated>2018-11-13T15:37:22.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*MXHo6Blns-933o3JSADRcg.png" /></figure><h3>UXDI Project 1 — Retrospective</h3><p>Project Name: PACKNGO a travel app with you in mind.</p><h3><strong>The Beginning.</strong></h3><p>I was given the topic ‘Travel’ by my partner and at first I thought that’s a really great topic because I have so many ideas about Travel too. Planning a trip can be such a tedious activity and having to juggle so many websites and information overload, what if we could have an app that solves this?</p><h3>Method in the madness.</h3><p>It seemed a little unnatural to me that I was giving an interview first, without really knowing what the problem was. But rather I was going to use my interview cases to identify the problem and create the hypothesis.</p><p>I have to search multiple platforms just to find things to do locally</p><p>Skyscanner is very convenient, everything is there for you to make an informed decision.</p><p>In summary, here’s what I learnt from the user interviews:</p><p>1. <strong>Everybody has a story to tell</strong> — let the user tell you their story and follow up on the behavioural aspects that are important to your research.</p><p>2. <strong>Stay Neutral</strong> — it’s so easy to fall into the “I know it” trap by only gathering only the answers you want to hear. This may cause your topic to be pigeon holed, without really uncovering the broader themes.</p><p>3. <strong>Same Same but different</strong> — It’s ok to have different questions for different users, because we’re still exploring at this stage of the design process.</p><p>4. <strong>Dig Deeper </strong>— At times I was too task focused to get through all my questions, rather than pausing and reflecting on what the user has answered and if we truly know “the why” behind their action or words?</p><h3>Surprise Surprise…and the results:</h3><p>Mapping out the user responses was a relatively fun task because I love categorizing and re-organizing. It did get a little tricky at times, when the categories were either too huge, or if I had some outlier responses that seemed to need a category entirely of its own.</p><p>What was surprising to me was that I was able to actually find similarities across my user interviews, especially if I zoomed in on their positive or negative experiences of travel.</p><p>Two natural themes emerged around the flexibility of flight searches and not knowing what activities can be done in an unknown location which led me to my problem statement and Hypothesis:</p><h3>Problem Statement:</h3><blockquote>Sharon needs an easy way to plan her trip based on her preferences, because current travel apps don’t search based on travel profiles.</blockquote><h3>Hypothesis:</h3><blockquote>By creating a customizable savable travel profile, Sharon can plan her trips with a predictive search that shows her travel destinations and activities catered to her preferences.</blockquote><p>The App and Prototype</p><p>Here were some of my initial sketches, where I designed a sign-up page and lso a basic tutorial to guide people through my app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*Lk3f9uoP_uaf8ZXQYzuRfQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*IB4l_cjpmw_201D-t18pmA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*JaLBwXikRt3fv2yMl2ZgOA.jpeg" /></figure><p>Upon testing with users, I received multiple rounds of feedback. Such as:</p><p>a) some screens were too noisy for a mobile app</p><p>b) people weren’t keen to sign up at the first stage without knowing what the app does (I decided to embedded this sign-up feature on a later page)</p><p>c) tutorials weren’t really necessary if we could guide the user as they went along</p><p>d) having suggestions on unique activities upfront was a desired user request.</p><p>Here were my sketches after a few reiterations:</p><h3>PACKNGO version 2.0</h3><p>Additional features I would have liked to add on:</p><p>Allow for multiple travel profiles to suit the occasion</p><p>Ø For destinations and activities provided, this list would narrow down further as more travel details (e.g. Flight/Trip duration) were defined</p><p>Ø Allowing users to pre-book some activities are even add free activities to their itinerary</p><p>However I was given some sagely advice, to focus on 1 part of the design first or I may run out of time, and boy am I glad I took that advise. 😊</p><h3>What would I have done differently?</h3><p>Overall, I think I would have done more planning around the timeline of the project and the preparation. In retrospect, these are the areas I would want to improve.</p><p>·<strong> Presentation matters</strong> — Review the requirements closely and make sure the main points are communicated across. Practice it gets covered in the allowed time frame. Be cogent!</p><p>· <strong>Just Test it </strong>— Testing early was important to get more feedback. And keep testing against the problem statement and look at it from the user’s point of view.</p><p>· <strong>Edit Edit Edit</strong> — I only did about 2 reiterations of my prototype, but I should have tested the idea more widely against different people.</p><p>· <strong>Keep it Simple </strong>— I was very focused ensuring my sketches were detailed, but with rapid prototyping I have come to realize the advantage lies in the quick draft sketches on the idea and testing those ideas. Details weren’t needed yet, as you can speak to your users of the design and get their feedback. Identifying a simple flow from start to finish was important.</p><p>Week 1 was certainly an eye opener of the topics and projects to come. I’m looking forward to work on project 2 but at the same time I am a little apprehensive….what have I gotten myself into?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5b809071b5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>