<?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 Nina Ee on Medium]]></title>
        <description><![CDATA[Stories by Nina Ee on Medium]]></description>
        <link>https://medium.com/@ninaee?source=rss-83cd31a78a4e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8UoJApF0PpQdOrzh51g77A.jpeg</url>
            <title>Stories by Nina Ee on Medium</title>
            <link>https://medium.com/@ninaee?source=rss-83cd31a78a4e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:03:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ninaee/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[Building two digital products to deliver one service]]></title>
            <link>https://medium.com/govtechsingapore/building-two-digital-products-to-deliver-one-service-59c3c4f50cb6?source=rss-83cd31a78a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/59c3c4f50cb6</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[government-innovation]]></category>
            <category><![CDATA[product-design-process]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Nina Ee]]></dc:creator>
            <pubDate>Thu, 13 Feb 2020 02:38:28 GMT</pubDate>
            <atom:updated>2020-02-13T12:30:39.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*tQB6ZDl_FZjhIpfiVqaiqw.png" /></figure><h3>Part 1: Discovery</h3><p>After our success with <a href="https://blog.gds-gov.tech/how-we-made-applying-for-grants-easier-e24d8182a8f5">Business Grants Portal</a>, more government agencies have come to the GDS team for help with their grants systems, including the Ministry of Culture, Community and Youth (MCCY).</p><p>Working on the <a href="https://mccygrants.gov.sg/">MCCY Grants Portal</a>, presented an opportunity to improve on what we’d built for Business Grants Portal and solve new problems unique to the community grants landscape.</p><h4>Background</h4><p>There are two parts to the grant process — an applicant sends in an application and a grant officer processes it. The whole process was manual and tedious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Ue9o9eWN-gJHCZRTxZmmHQ.jpeg" /><figcaption>Photo credit: <a href="https://www.thepositivepsychologypeople.com/better-give-receive/">https://www.thepositivepsychologypeople.com/better-give-receive/</a></figcaption></figure><p>Our challenge was to design the grant process as a digital service, which involved building one digital product for applicants to apply for grants and one digital product for grant officers to process grants. Of course, we wanted to take out the tediousness and add some joy.</p><p>Here’s how we did it.</p><h4>How we decide what to build</h4><p>Most government agencies expect us to just take their existing forms and build a digital version of them. When we start our collaboration, we spend time explaining that digitalisation is about rethinking the service for a digital audience, not just digitising existing forms and processes — and their inherent pain points.</p><p>A large part of the groundwork we do to engage our stakeholders — explaining our process, involving them in workshops and co-design activities — happens during the Discovery phase of product development.</p><p>During Discovery, we aim to get a good enough understanding of who might use the product and what the opportunities are for improving the current situation. We may not be able to cover all parts of the current process in depth during the discovery phase, so we aim for an overview and in-depth exploration of the major issues — enough to determine what would be best addressed in our minimum viable product (MVP).</p><p>Building a complete solution will always take time. The public service version of an MVP usually means what we can build quickly to alleviate the biggest problems so that we can deliver value to our users and stakeholders fast.</p><h4>What happens during Discovery</h4><p>Every product is different, so the activities conducted during Discovery will change to suit the product. The objectives of Discovery remain more or less the same though and these were our objectives and activities for the MCCY Grants Portal.</p><ol><li><strong>Understand the current situation</strong></li></ol><p><em>Grant experience</em></p><p>Usually one of the first things we would do during Discovery is market or desktop research to get an understanding of the space we were in. However, the core team that started on this product worked on the Business Grants Portal, so we were starting from a strong foundation.</p><p>We knew that streamlining processes and reducing duplication of grants delivered great results for business grants, so right from the start, we explored the possibility of doing the same for community grants. Having a successful case study to reference also helped us demonstrate to our stakeholders how a cross-agency collaborative approach could make a real difference to the outcomes achieved.</p><p>There were also improvements or enhancements that we wanted to test out. For example, Business Grants Portal was organised by process — when an applicant logged in, they saw all the actions they could perform. But we knew from our usability testing that applicants’ <a href="https://www.nngroup.com/articles/mental-models/">mental model </a>was, “I have grant application XYZ and I need to submit a claim for it”, so they typically looked for the application and not the action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SrGGmZHU3j71krX7XHvutA.jpeg" /><figcaption>Business Grants Portal dashboard organised by process</figcaption></figure><p>While enhancements have since been made to Business Grants Portal, such a large change to the information architecture needed to be phased and prioritised. With the MCCY Grants Portal, we had the opportunity to build differently, test out alternatives and share our findings with the Business Grants Portal team.</p><p><em>Stakeholder groups</em></p><p>Piecing together our overview of community grants started with engaging our stakeholders from the various government agencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*TjUBputnd-OkUwf9oea5Lg.jpeg" /><figcaption>Getting to know our stakeholders and their grants</figcaption></figure><p>We met with officers who process grants and their managers in half-day sessions. We asked them to explain all their grants, policy objectives, target audience, outreach efforts, stages in the grant process and challenges they faced.</p><p>This helped us map out the different types of grants, find similarities and narrow down our focus for the MVP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*ZraiPxB7DPNw-NFlc13QnA.jpeg" /><figcaption>Mapping the grant landscape</figcaption></figure><p>More valuable than an overview was the rapport that we started to build with our stakeholders. It was important for them to meet the team, understand our various roles and how we work, and to see that we were genuinely interested in understanding their challenges and problems.</p><p>Trust comes from being transparent, honest and eliminating unnecessary middle layers. That’s how the GDS team works but it’s not always what our stakeholders have experienced. Making a connection with them early in the process and demonstrating our values and ways of working help us set baselines and expectations for our working relationship.</p><p><em>In-depth </em><a href="https://www.nngroup.com/articles/user-interviews/"><em>user interviews</em></a></p><p>Talking to people who apply for grants is the best way to identify opportunities for improvement. We asked them to walk us through their grant experience so that we could better understand how the process worked for them.</p><p><a href="https://www.nngroup.com/courses/journey-mapping/"><em>Journey mapping</em></a></p><p>Synthesis of the information we’d gathered started with mapping both the applicant and grant officer journeys with front line staff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*VlR7Uk1alav6QaA4uWU1bg.jpeg" /><figcaption>Mapping user and officer journeys</figcaption></figure><p>Involving stakeholders in the mapping process, in this case grant officers who had the most contact with and knowledge of what applicants go through, is a good way to get buy-in on the points in the journey that need improvement.</p><p>Mapping both the applicant journey and the grant officer journey at the same time helped us to understand how the grant officer’s process impacted the applicant’s experience and vice versa. The grant officers were able to appreciate that making things easier for the applicant at certain points would result in making their jobs easier down the track. This was an important insight to support changes to policy and process that would deliver a better service.</p><p>We could see from the work done thus far that streamlining the process would deliver greater efficiencies, enable us to get more grants on the system quicker and provide applicants with a more consistent experience. So we focused these mapping sessions on finding similarities in the processes across grants.</p><p><strong>2. Explore new ideas</strong></p><p>After getting as good an understanding of the current situation as possible, we had lots of ideas we wanted to test.</p><p>An example was the dashboard page or the page an applicant would see when they logged in, where we tested out a different information architecture to better suit applicants’ mental model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mjzA9tO2qMPoIVtgAXk20Q.jpeg" /><figcaption>Iterating the dashboard design</figcaption></figure><p>As we were building two products, we tested prototypes for applicants with applicants and prototypes for grant officers with grant officers.</p><p><strong>3. Determine what the MVP should be</strong></p><p>Following our design and technology explorations, feedback from stakeholders and applicants and several iterations, we had a reasonably good idea of what our MVP should be.</p><p>The next task was to create a product backlog and start prioritising features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*4Oy2uirUR236ljQ2zmBffw.jpeg" /><figcaption>Facilitating conversations and working through priorities</figcaption></figure><p>As we were still working without a product owner, we facilitated product vision and prioritisation workshops to get all our stakeholders on the same page. We used prioritisation techniques such as <a href="http://www.uxforthemasses.com/5-techniques-prioritising-features/">buy a feature</a> and <a href="https://www.nngroup.com/articles/dot-voting/">dot voting</a> to help our stakeholders talk through their differing priorities and come to a consensus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*-OcY5GPpIkJVCMcr_giDDA.jpeg" /><figcaption>Coming to an agreement on objectives, KPIs and prioritisation</figcaption></figure><p>Setting clear and measurable objectives at the start was crucial to ensuring we were collecting the right data for reporting. As team lead, it was important for me to be able to quantify the value the team delivered and ensure they were getting recognition for the work they were doing.</p><h4>From Discovery to Development</h4><p>Armed with our product vision and prioritised product backlog, we had both the direction and the plan clearly articulated to guide us as we started to build our MVP.</p><p>We may only have a Discovery phase at the beginning but discovery activities continue during the Development phase as needed.</p><p>If you’d like to learn more about how designers and developers work together in our team, stay tuned for Part 2: Development.</p><p>If you’d like to build digital products and services from scratch and are interested in working for the public good, get in touch with <a href="https://medium.com/u/b4e25e2ffb5b">Soh Wendy</a>, <a href="https://medium.com/u/776388c87aa0">Janice Tan</a> or <a href="https://medium.com/u/db7cdbf5c7ff">Steven Koh</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59c3c4f50cb6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/govtechsingapore/building-two-digital-products-to-deliver-one-service-59c3c4f50cb6">Building two digital products to deliver one service</a> was originally published in <a href="https://medium.com/govtechsingapore">GovTech Singapore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we made applying for grants easier]]></title>
            <link>https://medium.com/govtechsingapore/how-we-made-applying-for-grants-easier-e24d8182a8f5?source=rss-83cd31a78a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e24d8182a8f5</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[business-grants-portal]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Nina Ee]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 00:01:19 GMT</pubDate>
            <atom:updated>2017-09-05T01:56:50.768Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>A Business Grants Portal Retrospective (Part 1)</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*e6YqUklLvZaD1SCc7qQd6A@2x.png" /></figure><p><a href="https://www.businessgrants.gov.sg/">Business Grants Portal</a> was built to make it easier for businesses to find and apply for government grants. With <a href="https://www.smeportal.sg/content/smeportal/en/moneymatters/grants.html">almost 30 government grants</a> available to Small &amp; Medium Enterprises (SMEs) in Singapore, businesses looking for a grant can take as long as 3–6 months to figure out which one meets their needs.</p><p>That’s why we’ve simplified grant application in these 3 ways.</p><h3><strong>1. One place for business grants</strong></h3><p>Business Grants Portal aims to bring government grants for businesses onto a single portal. We have 6 of the most popular grants on our site now and are working hard to add more. This greatly reduces the number of sites you need to trawl through to find the right grant.</p><h3><strong>2. Just 3 questions lead to the right grant</strong></h3><p>Let’s face it, reading up on all the grants available to businesses isn’t a lot of fun. That’s why with our grant selector, you just answer 3 simple questions about your business and we’ll lead you to the right grant application form straightaway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HxuvRvrthqI_rSYN5anjiw.png" /><figcaption>Get to your grant in 3 easy steps</figcaption></figure><h3><strong>3. Applications are routed automatically</strong></h3><p>Not sure which government agency gives out grants to your business? No problem. Leave the hard work to us.</p><p>We’ve streamlined similar grants that are administered by different government agencies. Simply apply through the portal and we’ll route the application to the right agency. Easy.</p><h3><strong>Our journey so far</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4tN33_UH-LMtKF2qkDjHDg.png" /></figure><h3><strong>Challenges, triumphs, lessons learnt</strong></h3><p>As we finish Phase 1 of development and prepare for Phase 2, here are some thoughts from the team on what we’ve achieved so far.</p><p>“Working on a large-scale project like Business Grants Portal, I’ve gained a better appreciation for Agile development and our team has built up their tech capabilities. More importantly, so many SMEs have benefitted from our portal. Our work makes it easier for them to innovate and helps to bolster the economy.” — Lim Zui Young, Developer</p><p>“It was challenging to transition new members into the team as some of the more established team members moved on to other projects for Ministry Of Manpower (MOM) and Workforce Singapore (WSG) but the new guys have stepped up and are performing well. It’s also great to see the number of grant applications going up every month!” — Lim Hoon Ling, Business Analyst</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/0*hRoIQwwz2exAmUH8." /><figcaption>Unit and feature tests can be seen as the friction that slows down product development</figcaption></figure><p>“Initially, I thought removing unit and feature tests would allow the team to develop faster. But I soon learnt that without friction, quality is compromised and your product shreds into pieces as it lands. People who don’t understand Agile might think friction slows down delivery but it is there to ensure your product lands safely.” — Goh Yew Lee, Developer</p><p>“SMEs contribute nearly 50% of our GDP while employing 70% of our workforce. The importance of helping them grow and flourish, both domestically and overseas, cannot be overstated. It’s our privilege to be given this opportunity to support their growth. Looking forward to creating more possibilities with tech! The best has yet to come! :)” — Steven Koh, Agile Coach</p><p>“In order to deliver what users really need, it’s important to have a plan but it’s even more important to be adaptable to change. Agile allows us to develop the product iteratively, so we can adapt to changes from agencies and feedback from users. It’s the only way we can deliver a product that enables SMEs and agencies to improve their productivity.” — Poh Kah Kong, Scrum Master.</p><h3><strong>What’s next?</strong></h3><p>We’re proud of the businesses we’ve helped so far. We’re also excited about the new features and improvements planned for Phase 2, from exploring chat bots to better fraud detection measures.</p><p><strong>If you have any ideas on how we can improve our current grant administration, leave a comment or </strong><a href="https://www.businessgrants.gov.sg/feedback"><strong>drop us a line</strong></a><strong>.</strong></p><p>Want to find out how our Agile co-sourcing approach helped us deliver Phase 1 of Business Grants Portal with a smaller budget and in a shorter time than the original Waterfall outsourcing estimate? Check out <a href="https://blog.gds-gov.tech/our-4-secrets-of-successful-software-delivery-8bb931144a9f">Part 2 of our Business Grants Portal Retrospective</a>.</p><p>Special thanks to <a href="https://medium.com/u/7bed02cc2c26">Alvin Tan</a> and <a href="https://medium.com/u/1781e38bf0fb">Joel Tai</a> for the awesome timeline and header image.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e24d8182a8f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/govtechsingapore/how-we-made-applying-for-grants-easier-e24d8182a8f5">How we made applying for grants easier</a> was originally published in <a href="https://medium.com/govtechsingapore">GovTech Singapore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 easy ways to improve product content fast]]></title>
            <link>https://medium.com/govtechsingapore/5-easy-ways-to-improve-product-content-fast-98aab4341089?source=rss-83cd31a78a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/98aab4341089</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[business-grants-portal]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Nina Ee]]></dc:creator>
            <pubDate>Tue, 04 Oct 2016 02:41:51 GMT</pubDate>
            <atom:updated>2019-04-12T04:26:50.624Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Jx1Sunhszgo67GZh.jpg" /><figcaption>Photo credit: <a href="https://jerichowriters.com/feature-76-start-writing-a-novel/">https://jerichowriters.com/feature-76-start-writing-a-novel/</a></figcaption></figure><p>Content design came to <a href="https://www.businessgrants.gov.sg/">Business Grants Portal</a> fairly late in the game. When I joined the team, the beta was out with one grant. Several others were in production, with usability testing going on the week I started.</p><p>Most people said, ‘the experience is great, doesn’t look like a government site at all but the language could be clearer’. I obviously had my work cut out for me.</p><p>So when your product is pretty far down the development road and launch is just around the corner, what are some easy ways to quickly make content more understandable?</p><h4><strong>1. Simplify</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rN4sgCBz-tsiyHzejdmkig.png" /><figcaption>Take out unnecessary words</figcaption></figure><p>The first thing I do with any project is to focus on the language. Eliminate unnecessary words, replace long words with short ones and break up long sentences.</p><p>Don’t forget to look at punctuation too. If you need anything other than commas, full stops and the odd colon, maybe you can simplify that sentence.</p><h4><strong>2. Get active</strong></h4><p>Ensure that wherever possible, you’re using the <a href="http://www.quickanddirtytips.com/education/grammar/active-voice-versus-passive-voice">active voice</a>. It makes content more concise and direct.</p><p>We always talk about content being a conversation. Using the active voice makes it easier to achieve a friendly, conversational tone. Your content will sound like a real person is talking, instead of <a href="http://www.urbandictionary.com/define.php?term=Corporatese">corporatese</a>.</p><h4><strong>3. Be consistent</strong></h4><p>With no one keeping tabs on the style, content becomes riddled with inconsistencies. Things like which words are capitalised, what headings look like, when to use sentence case or initial caps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDXJjbe6OZmElokSBoihww.png" /></figure><p>These might seem small but can be jarring to the people who use your product. So seek them out and start putting some rules in place.</p><h4><strong>4. Focus on flow</strong></h4><p>If you’ve been making all these tweaks one screen at a time, take a step back and look at the big picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PlN0XkWkq012Kydd9Ffuqw.png" /><figcaption>I take screengrabs and lay them out in Sketch</figcaption></figure><p>Does your end of the conversation hold up as people go through their journeys? Are you leading people to where they need to go? Are you giving them useful information at the right time? Does the screen you’re looking at make sense given where people are coming from and where they’re going next?</p><h4><strong>5. Watch your tone</strong></h4><p>You’d welcome someone cheerfully but it probably isn’t best to deliver an error message equally cheerfully.</p><p>Find the potential pain points or disappointments and do what you can to smooth them over. There’s a pretty big difference between being told ‘your application was unsuccessful’ and ‘you’ve been rejected’.</p><p>I like to pay particular attention to error messages. If someone has triggered one, they’re in a situation that could easily become a pain point. So how you talk to them and help them resolve the issue is important. You don’t want to make them feel like it’s their fault — even if it is. You want to helpfully guide them back onto the right path. The right tone can often make or break the experience.</p><p>So 5 quick ways to take your content from distracting to half-decent. Delightful is a whole other level that I’ll save for another blog post. Whether you’re a writer or not, give these tips a go and leave a comment if they help you make your content better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98aab4341089" width="1" height="1" alt=""><hr><p><a href="https://medium.com/govtechsingapore/5-easy-ways-to-improve-product-content-fast-98aab4341089">5 easy ways to improve product content fast</a> was originally published in <a href="https://medium.com/govtechsingapore">GovTech Singapore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>