<?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 Christiana Lai on Medium]]></title>
        <description><![CDATA[Stories by Christiana Lai on Medium]]></description>
        <link>https://medium.com/@christianalai?source=rss-3ffd8f4674be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uBq6c65WiyQ39A7ccRbPNg.png</url>
            <title>Stories by Christiana Lai on Medium</title>
            <link>https://medium.com/@christianalai?source=rss-3ffd8f4674be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:08:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@christianalai/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[6 Things I Learned at ProtoHack NYC]]></title>
            <link>https://medium.com/@christianalai/6-things-i-learned-at-protohack-nyc-23ddf3b9ed28?source=rss-3ffd8f4674be------2</link>
            <guid isPermaLink="false">https://medium.com/p/23ddf3b9ed28</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Christiana Lai]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 22:06:10 GMT</pubDate>
            <atom:updated>2018-04-17T15:00:14.793Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>My Hackathon Post-Mortem</strong></h4><p>Yesterday I participated in my very first code-free hackathon. The event is intended for the non-technical folk who wanted to get their EdTech idea in front of angel, VC and corporate investors, as well as industry professionals. Although the event lasted 12 hours, the real “hacking” was only for 5 hours where my teammate, <a href="https://medium.com/@dennisli_43466">Dennis Li</a>, and I had to ideate, design, prototype, and create an impressive 90 second pitch deck. Although my teammate and I didn’t place, I certainly came away with valuable insight about myself and about how to approach future hackathons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SjHt02NdYwfG42BlmpcxSw.jpeg" /><figcaption>Reviewing key features after doing a session of Crazy Eights</figcaption></figure><h4><strong>1. I Can Haul A**</strong></h4><p>Much of the event was spent getting to know other participants and getting a brief introductory course on design thinking so not a lot of time was allotted towards actual hacking. Actually, my team member and I didn’t get to designing screens until 2 hours before we had to submit our solution! Much of our time was spent on properly coming up with a problem that addressed the EdTech brief and then rapidly prototyping how we would solve the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPiNC09vLLixBDPB5bgfoA.png" /><figcaption>We decided to tackle the problem of how these students without proper guidance will miss out on opportunities they didn’t know were possible and universities are losing out on these potential students.</figcaption></figure><p>During our prototyping phase, it seemed minutes were quickly going by and we were stuck figuring out what to put on our first screen. At some point we realized that we were “pair designing” so instead we split up the the work and just occasionally bugged the other person when we needed a sanity check. Although we really wanted each element to be exact per Google’s Material Design guidelines, we just had to keep hauling. Which leads me to my next insight.</p><h4>2. Don’t Get Buried in the Details</h4><p>My teammate and I were really going for gold and considering the event’s name was a portmanteau of “prototyping” and “hacking”, we decided to assert our best efforts into creating high-fidelity visuals that communicated our solution to the problem. In doing so, we got caught up discussing things like “How should we display supplementary details? As an expansion panel or a slide-in side panel?” We had a lot of these little questions but ultimately we decided to just put what we think is best on the page and we’ll refine it later if time allowed.</p><h4><strong>3. Don’t Join a Team for the Sake of Joining</strong></h4><p>Most of the morning was spent chatting with other participants, understanding what their idea was, and considering joining forces. I made it a point to talk to all the people that came to the event with a problem already in mind to see if it was something I would be interested in prototyping for. One group had an interesting idea of a lesson plan hub where K12 teachers would be able to connect with other teachers and get critique or input on their lesson plans. I heard a lot of ideas that morning but I was the most enthused with this one. Unfortunately that team decided to bow out. So instead of forcing ourselves to prototype for an idea that didn’t move us, my teammate and I decided to ideate ourselves. This is when Dennis and I came up with Compass, a digital guidance counselor. I was pumped! 💪</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*yLCnKSEi2olbVjbCXcDmfQ.png" /><figcaption>To combat the problem of not having proper guidance during the college application process, our solution was to provide students with digital guidance during this critical time.</figcaption></figure><p>In the end, I’m glad it was just me and my teammate because we understood each other’s strengths and weaknesses and we were able to collaborate easily.</p><h4><strong>4. Use Your Time Efficiently</strong></h4><p>Most of the other teams had a predetermined idea ahead of time so they had some leeway but time was a tickin’ for me and Dennis. It’s obvious how to make the most of what limited time you have, but here is what worked for us:</p><p><strong>a) Timebox what you needed to accomplish</strong><br>Time management was key for a two-person team. Although we wanted to spend hours fleshing out our problem or perfecting our prototypes, it behooved us to work in the time we allotted to ourselves and start the next task.</p><p><strong>b) Just do it</strong><br>We often juggled ideas and went back and forth on whether we should do this or that. When you’re pressed for time and you’re wondering whether to do it? Just do it.</p><p><strong>c) Use design shortcuts</strong><br>In this day and age, there’s a high likelihood there’s a resource out there to help you. To lessen our workload, we looked at existing Sketch templates or searched for Sketch resources so that we didn’t have to recreate the wheel. Time saved is time earned!</p><p><strong>d) Only use tools you’re comfortable with</strong><br>At this particular event, they were pushing Balsamiq heavily with an added bonus of a $500 credit to some development service. Although it’s a great tool for rapid wireframing, Dennis and I were most familiar with Sketch and decided that was the tool we were going to use. Even though it might be cool try out a new tool, I would consider saving that for another day.</p><p>The following screens were done using Sketch to visually communicate our solution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNAuqr6nTv_9YpbeVmhCZg.png" /><figcaption>We chose key screens from our user flow to show. This screen is typically the first conversation you would have with your in-person guidance counselor.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-VGJWNrc6Gasf9k3f0vUQ.png" /><figcaption>With high school record integration, the solution would surface schools that were relevant to your preferences and be labeled accordingly with Target, Reach, or Safety.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDmFOeyVb8_mMV-Spn09RA.png" /><figcaption>One aspect of our solution involved pulling in deadlines and events from the schools the student is applying to so they can stay on track.</figcaption></figure><h4>5. Know Your Audience</h4><p>Here is where my teammate and I could have done a better job. Knowing that the judges were business-minded people, we should have spent more time on coming up with key points detailing how our idea would scale and how our solution could make money. This was our downfall because Dennis and I were caught up on the wrong aspects of this hackathon. We assumed that if there’s no coding then there was more emphasis on prototype design. We realized at the end that we needed to spend less time designing and more time discussing the business viability. Lesson learned!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNyMqi0Ab7F_jGTxOcomoQ.png" /><figcaption>We envisioned that our solution would be able to self-fund by providing key analytics to colleges on potential students that their currents efforts aren’t reaching.</figcaption></figure><h4>6. Crystallize Your Pitch</h4><p>At least at this business-first hackathon, you really need to know how to sell it. Since my teammate and I only came up with the idea that morning, we unfortunately didn’t have relevant materials, market research, or demos in advance like other teams did. But that didn’t stop us! We practiced our 90 second pitch up until the very last second to really solidify our solution.</p><h4>Reflection</h4><p>Overall, I really enjoyed Protohack’s idea of “no coding necessary” and would highly recommend it to anyone who already has a fleshed out idea and wants mentorship finessing their VC pitch decks for business leaders and to see if your business proposal stacks up. Since I’m more keen on testing my design chops than anything else, I’m really looking forward to attending hackathons that are geared more towards UX/UI to strengthen my design thinking and decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23ddf3b9ed28" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>