<?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 Kai Yang on Medium]]></title>
        <description><![CDATA[Stories by Kai Yang on Medium]]></description>
        <link>https://medium.com/@kaixyang?source=rss-cba64255e5c1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*huJY708vrL5SsLN9SqDJRA.jpeg</url>
            <title>Stories by Kai Yang on Medium</title>
            <link>https://medium.com/@kaixyang?source=rss-cba64255e5c1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:41:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kaixyang/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[Weeknotes #9]]></title>
            <link>https://kaixyang.medium.com/weeknotes-9-bf66433ad10f?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf66433ad10f</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 06 Dec 2020 11:29:14 GMT</pubDate>
            <atom:updated>2020-12-06T11:29:14.332Z</atom:updated>
            <content:encoded><![CDATA[<h4>November 30th — December 6th</h4><p>This week has been quite a rich week, where each day was vastly different from one another — I had a lot of fun!</p><h4>What did you experiment with?</h4><p><strong>Business emails<br></strong>This week I reported quantitative data results to the leadership team, where I had to write probably my first ever ‘business email’. I definitely spent longer than necessary on something that is a 1-minute read, but writing is unfortunately not my forte so I’m am looking to improve on this.</p><p>What I discovered through the editing process:</p><ul><li>Make your message clear: The ‘conclusion’ — point of why you’re even sending the email, should be the opening of your email (get to the point!).</li><li>Support the argument: Have a summary of results, with clear figures, that support that conclusion immediately after. In my case, I also attached an image of the results overview from the Survey tool I used.</li><li>Think about the reading experience: The image I attached, I had it in line with the email text, so readers can directly see the image — rather than have them click into an attachment.</li><li><strong>Bonus:</strong> Like any other email, have a high converting subject line — build anticipation from your audience from the moment they see it. Don’t be afraid to put in a bit of humour/punch! 👊</li></ul><h4>What was hard?</h4><p><strong>Ad hoc tasks<br></strong>I like to plan my day, and ‘tick of the checklist’. The first thing I do when I start work is open up the Trello board to work out what I want done today. So when ad hoc tasks appear — literally every day this week — my work momentum and spirit felt a bit compromised. This project in itself was an ad hoc task, an acknowledgement about having a more thorough project and sprint planning sessions has taken place, hopefully this situation can be managed better across the team.</p><h4>What was fun?</h4><p>Learning about the potential outcomes of Photoshop at SiSU Health. I will leave it at that. #SaiMatt</p><h4>What did you learn?</h4><p><strong>Closing the feedback loop</strong><br>As hinted earlier, I conducted a survey with customers to gather quantitative insights. Companies often just get customers to contribute to their business for their data insights, but they don’t close the feedback loop — they leave their customers hanging.</p><p>Closing the feedback loop is a way to keep customers engaged, and to make them feel like their contribution, such as actively filling out surveys, is bringing value to a business that they have invested in.</p><p>How I did it? Via email. It was very similar to the ‘business email’ mentioned above, with the key differences of:</p><ul><li>A different tone of voice — more friendly;</li><li>The opening sentence gives ‘conclusion’ in a way that empowers customers;</li><li>Have next steps outlined, what the business will action from their survey responses to build anticipation and ongoing engagement.</li></ul><p><strong>Containerise concepts<br></strong>This is how your product goes <em>beyond</em> MVP. You don’t want to experience featuritis when your needs to go live within a certain time. So you have the MVP that allows your product to be functional out first and following that, you gradually ‘plug in’ features/concepts that you’ve tested and built that make the product <em>better</em>. The key thing is, these new features do not affect your existing product, they’re ‘modular’ and can be put on existing pages. During the design of these concepts, it’s critical to be mindful of atomic design principles and the usage of the design system — keep things as simple as can be.</p><h4>Who did you talk to outside of your organisation?</h4><ul><li>Participated in a GA UX portfolio review as alumni. It was great to be able to give back to the GA community. Giving succinct feedback is something that can always be improved, glad I had the opportunity to work on that.</li><li>Junhan — An architect who is planning to make a transition into UX, I shared my career transition story with them.</li></ul><h4>What do you wish you could have changed?</h4><ul><li>Ensuring that the design system components are always used. <strong><em>Always</em></strong>. (You can probably guess one of this week’s ad hoc tasks now)</li></ul><h4>What are you looking forward to next week?</h4><p><strong>Last week: Onboarding experience being confirmed and executed in designs</strong></p><p>Tick! We researched best practices then ideated on 3 different concepts then chose one to continue with — based on impact/effort. During an early concept discussion with another design team member, they were quite adamant about one interaction that the onboarding experience should have, which differs from our initial concept. So, rather than listening to ‘one person’, we performed quick sense checks via user testing to validate our design assumptions. And it turns out, they were the only person who felt that way. Classic learning: Always talk to people!</p><p><em>This week: Data visualisation of HRA</em></p><h4>Personal Grateful Moments that I want to call out:</h4><ol><li>Went on a peaceful walk with my Mum, Sister and her 18-month daughter</li><li>Having emotionally supportive friends</li><li>Having that one Friend who overpacks— 3 extra umbrellas definitely came in handy when you’re hiking during a storm.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf66433ad10f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #8]]></title>
            <link>https://kaixyang.medium.com/weeknotes-8-b358b5306a1d?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b358b5306a1d</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 29 Nov 2020 12:47:35 GMT</pubDate>
            <atom:updated>2020-11-29T12:47:35.834Z</atom:updated>
            <content:encoded><![CDATA[<p>November 23rd — 29th</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ntQIMHMONjnddcKnmIoIeA.jpeg" /><figcaption>First beach visit in 2020!</figcaption></figure><h4>What did you experiment with?</h4><p><strong>Onboarding<br></strong>I joined the Portal project in the last fortnight, the Portal is going through staged releases, where it eventually is pushed to its ‘ideal state’. With this MVP approach, this buys us a bit more time to continue to improve and design for a user-centric experience whilst having the business goals in mind. Sindhu and I noticed that the current Portal onboarding experience is lacking, and onboarding as an experience is imperative for user engagement. After investigating ‘onboarding best practices’, we are in the process of fleshing out onboarding further — exciting times ahead!</p><h4>What was hard?</h4><p>Balancing <em>responsibility</em> and <em>control</em>.</p><h4>What did you learn?</h4><p><strong>Taking a Break</strong><br>I took a break from Weeknotes to clear out my mind amidst personal turbulent times. At first, I was quite disappointed in myself for pausing this habit, since this was a personal goal that I wanted to upkeep. However, there is only so much you can mentally take on, without jeopardising your day-to-day attitude. Coming to terms that this break was only temporary, so I have the capacity to take on new / continue things was a challenge — something that I actually tell people a lot, but when it came to myself it definitely was a mental challenge to not be too harsh on myself. Always easier said than done — but I definitely feel a lot more like myself after having time to rejuvenate.</p><h4>What would you have liked to do more of?</h4><p><strong>Showcase<br></strong>This week I led my first client showcase. Overall, it went well and was a worthwhile experience, however, during Q&amp;A — from the questions that were asked — I realised I should’ve had a slightly different spin/focus on the presentation. Key takeaways:</p><ul><li>Know your audience and their business focus</li><li>Be a more engaging storyteller with a ‘sales’ pitch where necessary</li></ul><h4>What are you looking forward to next week?</h4><ul><li>Onboarding experience being confirmed and executed in designs</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b358b5306a1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #7]]></title>
            <link>https://kaixyang.medium.com/weeknotes-7-64aef8edd4c9?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/64aef8edd4c9</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Mon, 09 Nov 2020 06:58:48 GMT</pubDate>
            <atom:updated>2020-11-09T06:58:48.117Z</atom:updated>
            <content:encoded><![CDATA[<p>November 2nd — 8th</p><p>With the public holiday this week was slightly shorter and centred around these things:</p><h4>Copy</h4><p>I engaged in UX copywriting with two different parties — with Marta, our Chief Pharmacist and the Analytics/Engagement Team. This is where being a product designer is quite fascinating, where you’re <em>both</em> the specialist and not-the-specialist.</p><p>With Marta, the focus was to be pharmaceutically correct as all content needs to pass legality. The challenge of this task was to make ‘technical’ information digestible to users and visually be proportional in page layouts. Using dot points or tables where possible was great to make the content scannable and succinct.</p><p>With the Analytics/Engagement Team, we had a session where we worked on setting up the feedback loop emails and how they integrate on Klaviyo. Similar to user testing for design validation, this session was great to sense check the copy regarding service understanding, from team members who are quite removed from the designs/project. This was also an opportunity to clarify and unify any terminology, as terms used on from data triggers would be inconsistent or confusing when brought to light to customers.</p><h4>User Flow</h4><p>I worked on incorporating outstanding customer functions into the post MVP designs. I devised two different logics/set of blanket rules for the respective functionality.</p><p><strong>Lesson learnt</strong>: Always have the simplest solution. Consider dev effort. Quick user tests to sense check!</p><p>Initially I mapped out what I considered the ideal user experience, where users have control over their choices. However after a discussion with Product, the dev effort was considerably high so I then modified it to be simpler. <strong>In retrospective, giving users too much power and variation over what is in fact a simple process is unnecessary.</strong> Keep the screen count low!</p><p><strong>What are you looking forward to next week?</strong><br>This question is slightly hard to answer project/task-specifically, as with the recent shift in company priorities I believe I would be on a different project quite soon.But on a broader sense, to improve and learn as a product designer always!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64aef8edd4c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #6]]></title>
            <link>https://kaixyang.medium.com/weeknotes-6-45451ad21361?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/45451ad21361</guid>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Tue, 03 Nov 2020 10:12:37 GMT</pubDate>
            <atom:updated>2020-11-03T10:12:37.365Z</atom:updated>
            <content:encoded><![CDATA[<p>October 19th — November 1st</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JeqZ51FLJqclpk_-TVgjQA.jpeg" /><figcaption>Participated in the Alternative Halloween Carving Competition at work!</figcaption></figure><p>Hello again! This entry is a catch-up double post — the easing of restrictions here in Melbourne has disrupted my writing routine as I felt the need to prioritise my personal relationships over ‘personal development’. But, weeknotes isn’t forgotten so here it is!</p><h4>What did you experiment with?</h4><ul><li><a href="https://lensstudio.snapchat.com/"><strong>Lens Studio</strong></a><strong> <br></strong>Following the completion of my Introduction to Augmented Reality and ARCore course by Coursera, I wanted to have an instant feel of AR interfaces so I investigated Lens Studio. I’ve been off Snapchat for years so I wasn’t aware of the tech/AR progression and I was quite impressed! With its AR resources being publicly accessible, I can see how it’d help the engagement of the app — where its users also creates content for the app. I’m still following the template guides at the moment, hopefully I’ll be able to experiment further with my own flavour.</li></ul><h4>What was hard?</h4><ul><li><strong>Finding balance<br></strong>During the past fortnight there seemed to be an abundance in meetings and discussions. Though they are important for project advancement, the turnaround time between meetings made it hard to realise and test ideas — hence move on to the next idea.</li></ul><h4>What did you enjoy?</h4><ul><li><strong>Common Design sessions</strong><br>I’ve been facilitating internal design sessions where we share and critique UX/UI best practices within the design team. We look at a different topic or in depth article each time with hopes that they would assist us in formalising our own design guidelines. Engagement from the team has been great, which makes my facilitator role easier. We have extended the duration of these sessions since they have value to the team!</li></ul><h4>What was fun?</h4><ul><li><strong>Sending out launch emails</strong> — it finally happened!</li><li><strong>Ultimate Frisbee!</strong></li></ul><h4>What did you learn?</h4><ul><li><strong>Online repurposing<br></strong>We had a Lunch &amp; Learn with <a href="https://www.linkedin.com/in/marshwah/">Luke Marshall</a>, where he spoke about making content responsive to the platform you’re publishing it, rather than always creating new content with new information — because it can get taxing! This resonates with what John from GA had said, how one case study isn’t just one piece of content, but you can break it up into endless pieces and formats.</li></ul><h4>Who did you talk to outside of your organisation?</h4><ul><li><strong>Angel</strong> — Spoke about my internship experience and we’re both interested in AR! <br>My advice for people doing internships: Be hungry and soak up as much as you can during the limited time. Think of it as a learning experience and opportunity to help you land your next role.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45451ad21361" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #5]]></title>
            <link>https://kaixyang.medium.com/weeknotes-5-4bf0b62ed936?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bf0b62ed936</guid>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 18 Oct 2020 05:35:47 GMT</pubDate>
            <atom:updated>2020-10-18T05:35:47.245Z</atom:updated>
            <content:encoded><![CDATA[<p>October 12th — 18th</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*arYHDUlOyLQF0dkz.jpg" /><figcaption>Mario Kart Live: Home Circuit -<a href="https://www.kotaku.com.au/2020/10/mario-kart-live-home-circuit-looks-like-fun-if-you-have-the-space-and-money-for-it/"> Image Source</a></figcaption></figure><p>This week’s weeknotes will be short and sharp.</p><h4>Highlights of the week:</h4><ul><li>Retro x 2</li><li>Showcase</li><li>Went to the dentist</li></ul><h4>What did you experiment with?</h4><p><strong>AR</strong><br>I started an Introduction to AR course outside of work. This is something that I’ve become quite interested in — triggered by my personal experiences with healthcare (both traditional and telehealth). To me, the realm of VR/AR/XR holds the potential to mediate the current barriers imposed onto creating human-centred health experiences.</p><p>My recent appointment with my psychologist took place in my bedroom aka the home office over Zoom. For such a personal and introspective situation, the environment I was in made me feel quite the opposite. I am quite excited to see the development of VR/AR/XR in healthcare — the ambitious side of me wants to contribute to this.</p><h4>What are you looking forward to next week?</h4><p><em>From last week: Deliverables of launch plan<br></em>As part of our launch plan, we designed the feedback loop of the service. To do so we created an overall logic flow of the E2E journey and mapped out the key events that would trigger automation. Key action and learning from our discussion with Analytics was to A/B test the content engagement — this was something we had not considered prior to the conversation. <br>Remember: During the launch / early phase of the product it is important to optimise learning.</p><p>Next week:</p><ul><li>Fab Dev Review Livestream</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bf0b62ed936" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #4]]></title>
            <link>https://kaixyang.medium.com/weeknotes-4-9df0e45525c9?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9df0e45525c9</guid>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 11 Oct 2020 04:59:25 GMT</pubDate>
            <atom:updated>2020-10-11T04:59:25.639Z</atom:updated>
            <content:encoded><![CDATA[<p>October 5th — 11th</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKXvd6nncdWyXzhu8TzwRg.jpeg" /><figcaption>Had the classic lying on grass and felt appreciative moment ✌</figcaption></figure><h3>The week:</h3><h4>What was hard?</h4><ul><li><strong>Finding the ‘dream job’</strong><br>We do OKRs at work and was tasked with having a plan for how to achieve personal speciality. The overarching question was<em> ‘What is your dream job?’</em> Although knowing that this task is for the upcoming quarter, labelling something with ‘dream job’ after having recently made a career change was honesty quite overwhelming. I broke it down with my counsellor, as she gave me thoughtful advice on rather than thinking of the question as THE lifetime dream job, remember focus on the present — the short term goals. <strong><em>Focus on what you know for certain at the moment — what you like and/dislike and use those as the guiding framework.</em></strong></li></ul><h4>What did you enjoy?</h4><ul><li>Seeing the team in flesh after 3 months — whilst abiding COVID regulations.</li></ul><h4>What did you learn?</h4><ul><li><a href="http://paulgraham.com/ds.html"><strong>Do things that don’t scale</strong></a><strong><br></strong>Some things don’t happen after you’ve found product-market fit and have scaled up, but they happen at the <em>very beginning</em>. Paul Graham’s article outlines the various elements, but the one that appealed to me the most was <em>creating user delight</em>. My longest job ever is in retail, so I can resonate anecdotally on what’s is like to ‘make a customer’s day’— and honestly, as a result my day was also made, since my service and the products I’m working with not only solved the user’s problem but also created a personal connection. Graham highlights that many start-ups don’t have this focus for a number of reasons, such as waiting for scaling and founders not having experienced this themselves; this made me realise that endorsing for a user-centric approach should always be pushed to be prevalent in design practice.</li><li><strong>Organisation is key</strong><br>Given the nature of this week’s deliverables — conditional tasks, a clear sequence of tasks became imperative. Rather than having just a kanban board — with task broken up individually; we were flexible and found what works best for us — good ol’ Google doc. This documentation of process made it easier for us to track updates and work of the project.</li><li><strong>How to email people</strong><br>Have a clear ‘call to action’ prompt at the beginning of your email message to manage expectations and, call to action from users.</li><li><strong>Digital Marketing<br></strong>I’m thinking of writing up a more detailed case study type piece when I’m ready, but for now — digital marketing can be as complex and as simple as you’d like it to be. But the high level principles are the same, focus on: the problem/what are you solving, who your users are, what language do they use, hypotheses and quantifiable measurables to monitor success.</li></ul><h4>What are you looking forward to next week?</h4><ul><li><em>Learning how to launch a product and optimisation strategy</em> — Product launch is very exciting, this week we looked at resources on product-market fit and digital marketing. My key takeaway from the research, be prepared to fail and optimise user tests for learning — find out what you don’t know as early as possible.</li></ul><p><strong>Next week:</strong></p><ul><li>Deliverables of launch plan</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9df0e45525c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #3]]></title>
            <link>https://kaixyang.medium.com/weeknotes-3-acd7c0b37d10?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/acd7c0b37d10</guid>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 04 Oct 2020 08:48:44 GMT</pubDate>
            <atom:updated>2020-10-04T08:48:44.684Z</atom:updated>
            <content:encoded><![CDATA[<p>September 28th — October 4th</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GnBI67Q9gGMSLmN5FvTjGw.jpeg" /><figcaption>Made lanterns in the spirit of Mid Autumn Festival! #quarantineartsncraft</figcaption></figure><p>This week’s entry is a shorter one, as the week has been quite production/tools focused.</p><h4>What did you experiment with?</h4><ul><li><strong>Feedback session format</strong><br>As a project team, we had a 2hour feedback session rather than the usual Figma/Slack comments or whimsical ‘when there’s some free time in the diary’. I much prefer this verbal and interactive method, as much as it is a feedback/critique session it’s also an opportunity to bounce ideas and to quickly do mockups together. I personally think that if there’s a whole thread of comments addressing one thing and its iterations, then you’re better off having a quick call to avoid any confusion — given remote conditions.</li></ul><h4>What did you enjoy?</h4><ul><li><strong>Attending Henry’s Life after Le Wagon talk</strong><br>Having completed General Assembly’s UXDI, it was interesting to hear different voices on the job hunting process — this time from a Dev perspective. The talk motivated me to want to do better in what I do. It’s a tough job market at the moment, and I have a job. I want people to recognise that I deserve my position; my work should be able to speak for itself.</li><li><strong>Thais sharing her further investigation on Nir Eyal’s Hooked Model</strong><br>I’m forwarding to the continuation of this presentation, where she would lead a workshop on how to assess the business using the questions from Hooked Model.</li></ul><h4>What did you learn?</h4><ul><li><strong>Stick to E2E for MVP</strong><br>As we have had increased engagement with the Product Team, interrogation on non-MVP features have also increased. Although these discussions have been really useful and assisted in understanding the scope of the product, it is important to focus on MVP and being able to push back on Product where it is necessary to park ideas until the next release.</li></ul><h4>What would you have liked to do more of?</h4><ul><li><strong>Talk to people outside of my organisation<br></strong>A twist on the usual ‘Who did you talk to outside of your organisation’ question. Replying to messages is in the Priority Backlog!</li></ul><h4>What are you looking forward to next week? (from last week)</h4><ul><li><em>Learning how to launch a product and optimisation strategy</em> — given project timeline changes, this has been rescheduled to happen this coming week!</li></ul><p><strong>Next week:</strong></p><ul><li>Facilitating a remote design studio for LFIA</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acd7c0b37d10" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #2]]></title>
            <link>https://kaixyang.medium.com/weeknotes-2-5764ab69fc48?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5764ab69fc48</guid>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 27 Sep 2020 11:32:17 GMT</pubDate>
            <atom:updated>2020-09-27T11:32:17.708Z</atom:updated>
            <content:encoded><![CDATA[<h4>September 21st — 27th, 2020</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1T3xsoQZvp7Q4FYQMeVjA.jpeg" /><figcaption>Canadian Poutine from Oh Boy! Food Truck</figcaption></figure><p><em>I am </em><strong><em>sorry not sorry</em></strong><em> for the above image. It was seriously the highlight of the week — Poutine at the Park!</em></p><p>The past two weeks have been of long days. This doesn’t quite register during the week since I’m ‘busy’ and ‘focused’, but I do feel it on the weekend.</p><p>One thing I decided to make a habit of is to do a Smiling Mind session during Screen Break. My previous practice got disrupted when I started my new role, and I definitely feel the difference. So, gotta get back to it!</p><p>I enjoy like the ‘activity’ sessions, where daily mindfulness can be understood in everyday simple tasks. I did one where it got me to focus on my food, its taste and the way I chew — something I didn’t pay attention to before.</p><h4>What did you experiment with?</h4><ul><li><strong>Engaging with the Product Team</strong><br>This was something that we addressed during last retro — to be bring in Product earlier so we can: collaborate more, be less siloed in our practices, understand where the <em>entire </em>Project Team is at to launch MVP. Knowing this also prevents design rework. We had a few check ins with Jade this week to walk through our flow and got another one scheduled coming Monday. These check ins also allowed us to consolidate our logic beforehand and subsequently together identify any gaps from all product, dev and design lenses.</li></ul><h4>What did you enjoy?</h4><ul><li><strong>Design team goals</strong><br> We got together and worked out what we want to achieve as a team. We have always shared learnings, but it was the first time where we shared ambition. I found that it was an interesting exercise to see how people’s personal interests reflected in what they suggested for the team. Defining these objectives together attunes team vision and they would provide a criteria of sorts for us to work and reflect on for the future.</li></ul><h4>What was fun?</h4><ul><li><strong>Usability tests<br></strong>When the user is also a wedding host and their personality shines through. Trying to keep a straight face to not give anything away is challenging.</li></ul><h4>What did you learn?</h4><ul><li><strong>Keep the same logic </strong><br>Don’t complicate things and keep the flow that has been tested with. This also makes things easier for dev.</li><li><strong>BA 101</strong><br>Jade hosted a great Lunch &amp; Learn session, she presented User Stories and Acceptance Criteria. I found both concepts quite straightforward — but user stories to me has a similar structure to problem statements, but in first person; so I feel more familiar with it. I am excited to see how an acceptance criteria would come to life, when measuring a real case study. I have lesser experience with implementing projects</li><li><strong>User Interview Questions</strong><br>Be sure to highlight the fact that full disclosure is not necessary <strong><em>before </em></strong>the interview. Practise your interview questions beforehand.<br>I did not frame one of the questions I asked the way I intended to and it came out the wrong way. Given the sensitivity of the topic it could have had a drastic outcome — but luckily our user was understanding and we moved on. Another way to look at it is also to give more time at the beginning to get to know your user and break the ice, that way they will be more comfortable talking to you too.</li></ul><h4>Who did you talk to outside of your organisation?</h4><p><strong>Jait</strong> — Initially a ‘LinkedIn coffee catchup’ but we’re pals now! Discussed both work and non-work related happenings.</p><p><strong>Alex</strong> — We caught up after Startmate. Alex was very candid about this own startup story — the success and failures of running a startup.</p><p><em>Key takeaways:</em><br>- Product-market fit is so important.<br>- the best way to learn about startups is to work at a startup.<br>In reflection after our conversation, for my interview I could have leveraged my technical understanding more, this would’ve strengthened my point of difference, given that most applicants have a management and/or law background.</p><h4>What are you looking forward to next week? (from last week)</h4><ul><li><em>Being more succinct during the handover to Dev</em> — Our handover got rescheduled to the coming week, but I have given written feedback this week so I am feeling more confident!</li><li><em>Running 10k! </em>— I did it! — I had previously made this milestone but due to time off from a tooth infection I had to work my way up again. So it felt good being able to achieve it!</li></ul><p>Next week:</p><ul><li>Learning how to launch a product and optimisation strategy</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5764ab69fc48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes #1]]></title>
            <link>https://kaixyang.medium.com/weeknotes-1-a562ce758446?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a562ce758446</guid>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Sun, 20 Sep 2020 12:06:56 GMT</pubDate>
            <atom:updated>2020-09-20T12:06:56.252Z</atom:updated>
            <content:encoded><![CDATA[<h4>September 14th — 20th, 2020</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_UjCFpzDi32jVppXfGJNWQ.jpeg" /><figcaption>Illustration: <a href="http://www.abbeylossing.com/">Abbey Lossing</a></figcaption></figure><p>Last week when I was drafting my personal OKRs, I decided to include ‘writing’ as an Initiative for my Objective of ‘developing as a digital product designer’.</p><p><em>Why?</em> I see it as a great reflective method and keeps track of the key moments that occur during the week. I keep a personal diary; architecture has always endorsed ‘design journals’, this practice is something I find very effective so I want to incorporate it into my professional learnings.</p><p>In all honesty, I previously attempted to do this a daily basis however I wasn’t too happy with the format and quality of writing. Then I came across a series of others’ Weeknotes and <a href="https://weeknot.es/weeknote-styles-61d957e58a4a">this post</a>, thus decided to restructure my reflections with the ‘Stretching Questions’ format.</p><p>Here’s my first Weeknote!</p><h4><strong>What did you enjoy?</strong></h4><ul><li><a href="https://sisuhealthgroup.com/health-of-a-nation-report-2020/health-of-a-nation-full-report/"><strong>Health of a Nation</strong></a><strong> presentation</strong> <br>Internal lunch &amp; learns / showcases are always great to see what is happening across the company. Seeing what was being presented was also exciting, as the design team can definitely incorporate the research for customer-centric products. Considering the scale and dimensions of data the Analytics Team was working with, it was impressive seeing it all come together!</li><li><strong>Volunteering for </strong><a href="https://living-future.org.au/"><strong>LFIA</strong></a><br>Outside of work, I have been volunteering my UX research skills with <a href="https://www.linkedin.com/in/suma-narayana/">Suma</a> and <a href="https://www.linkedin.com/in/trophic/">Rohan</a> for LFIA. This week we had a very productive session, where we developed our personas and customer journey map. I facilitated the synthesis of the customer journey map; it was a great opportunity to consolidate my understanding of this artefact from what I have already learnt and practised at work.</li><li><strong>The weekend sunshine! 🌞</strong><br>I am based in Melbourne, where we have endured 6 months of lockdown. So the weather was actually a big mood booster this weekend!</li></ul><h4><strong>What was fun?</strong></h4><ul><li><strong>Nat’s ‘unboxing stream’ 👟</strong><br>This happened during a ‘social break’ at work, given that we are working fully remote, I particularly enjoy these non-work-related sharing moments. (Taking and scheduling regular breaks is also part of a healthy practice!)</li></ul><h4>What was hard?</h4><ul><li><strong>Dev-Design Review</strong><br>I wouldn’t call this ‘hard’ but it’s definitely a new thing for me. As we are now in the delivery phase, our designs are getting built by the Dev Team and we need to provide feedback on the work they’ve done. I am familiar with the practice of design critique through architecture, however, giving feedback with a ‘Dev lens’ — with the correct terminology and level of technical detail — is something I am hoping to improve in!</li></ul><h4><strong>What did you learn?</strong></h4><ul><li><strong>The importance of colour and contrast for accessibility </strong><br>Already I have previously heard of this, it only registered when I was doing this <a href="https://www.skillshare.com/classes/DESIGN-RULES-Fundamental-Principles-Practices-for-Great-UI-Design/739408485/projects?via=search-layout-grid">Design Rules</a> Skillshare course — Joe the instructor frames achieving accessibility as a dialogue between colour <em>and</em> contrast, where contrast gives the colours you’re working with visual depth. This made me conscious that I previously overlooked accessibility when designing (shame on me), checking the contrast is only one Figma Plugin away but it will greatly improve the experience and maturity of designs.</li><li><strong>Documentation</strong><br>With the nature of the project scope and current phase, we found it hard to keep track of design changes and of why<strong> </strong>those changes were important — as information would supersede others. So we implemented a process of keeping a ‘decision log’, similar to the concept of this Weeknote, it’s to have design decisions in the one place and with dates, so you can refer back when you need to. Rather than just ‘pumping out work’, planning out and making sure you’re doing the <em>right</em> work is an important first step.</li></ul><h4><strong>Who did you talk to outside of your organisation?</strong></h4><p>Honestly, I usually don’t speak to this many people outside of work per week; but this week it <em>just happened</em>. This week also made me realise how much I like and miss talking to people and sharing experiences — something I would like to try and keep consistent.</p><p><strong>Markus</strong> — An aspiring UX/UI designer, we shared our stories of how we ‘found’ UX and talked about finding personal flavour as a designer.</p><p><strong>Joseph</strong> — We both embraced how this industry is very fast-paced and ever-changing; there is a need to upskill and develop professionally — in a fun and because you’re passionate way! <br>(Note to self: Read and share thoughts on the article that Joseph linked me to.)</p><p><strong>Kelvin</strong> — My past student from architecture who is considering making a career change into digital design. We shared frustrations on the architecture industry and what our personal values are as designers.</p><p><strong>Anna</strong> — We caught up and discussed my Startmate interview. I shared my ambition on maintaining Weeknotes and she said this practice and this ‘stretching questions’ format is something that Startmate also endorses (what a coincidence!)</p><h4><strong>What would you have liked to do more of?</strong></h4><ul><li><strong>Usability tests</strong><br>The more feedback the better — especially <em>before</em> the product is getting launched!</li></ul><h4><strong>What are you looking forward to next week?</strong></h4><ul><li>Being more succinct during the handover to Dev</li><li>Running 10k!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a562ce758446" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote Collaboration: Miro]]></title>
            <link>https://kaixyang.medium.com/remote-collaboration-miro-c45205ca1383?source=rss-cba64255e5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c45205ca1383</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[miro]]></category>
            <category><![CDATA[ux-design-tools]]></category>
            <dc:creator><![CDATA[Kai Yang]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 12:14:11 GMT</pubDate>
            <atom:updated>2020-07-16T12:14:11.972Z</atom:updated>
            <content:encoded><![CDATA[<p>Previously I had only used Miro to synthesise user interview findings — going remote has revealed more of Miro’s ability to me, and how it is quite the powerful collaborative tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KCEUeMDP0B9pebtDAynk3g.png" /><figcaption>Virtual ‘War Room’</figcaption></figure><h4>Keeping everything in the one<em> </em>place</h4><p>Team transparency at its finest. Our design team is all working in this space, with different projects happening, it is still possible to witness others’ learnings and gather intel even without direct communication e.g. My project team found another team’s colour coding system effective, so we brought that on board. <em>See what’s working for your peers and adapt! Learning is flexible.</em></p><p>For me personally, the day goes by so quickly that although I know we had completed a lot, it’s always motivating to see something tangible at the end of the day. And it’s all there in Miro. (Don’t forget to celebrate your wins!)</p><h4>Brainstorming (a Survey)</h4><p>As mentioned, never used Miro beyond interview affinity mapping prior to this remote experience. Similar to the process of affinity mapping user insights, we created a survey using Miro.</p><ol><li>List out all the things we want to learn from users <em>(Transcribe user interview, each insight on a separate post-it)</em></li><li>Theme questions to see what we’re looking to discover and see what are the overarching points of discovery <em>(Grouping to see the main goals, pain points)</em></li><li>Select key questions to form survey <em>(Select insights to form user personas)</em></li></ol><p>Using Miro allowed flexibility in the process, I previously would only use Google Docs to ‘write everything out’. But after having used Miro for this task, being able to arrange and rearrange ideas visually definitely wins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*7B9AndJn9KefPCtdbQvEBQ.png" /><figcaption>The survey! Can you guess the colour codes?</figcaption></figure><h4>Integrated Tools</h4><p>Tagging from my first point, it’s always good when one tool can do everything. Tool fatigue is real. Although I am still a huge fan of Notion and use it personally, being able to comment; create kanban boards and userflows to share with your team in the shared space is always a win.</p><p>There’s definitely more perks to Miro but these are the ones that stand out to me. Let me know what your ‘must-use-Miro-this’ things are!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c45205ca1383" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>