<?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 Richard Parayno on Medium]]></title>
        <description><![CDATA[Stories by Richard Parayno on Medium]]></description>
        <link>https://medium.com/@richardparayno?source=rss-fbd130e11e32------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2GJHUZBfDb_I3EF8a90gVw@2x.jpeg</url>
            <title>Stories by Richard Parayno on Medium</title>
            <link>https://medium.com/@richardparayno?source=rss-fbd130e11e32------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:40:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@richardparayno/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[Let yourself rest]]></title>
            <link>https://richardparayno.medium.com/let-yourself-rest-764da551da17?source=rss-fbd130e11e32------2</link>
            <guid isPermaLink="false">https://medium.com/p/764da551da17</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[self-care]]></category>
            <dc:creator><![CDATA[Richard Parayno]]></dc:creator>
            <pubDate>Wed, 14 Apr 2021 10:17:14 GMT</pubDate>
            <atom:updated>2021-04-14T10:17:14.821Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*ov4bmYGACfLqtkKM" /><figcaption><em>Image Source: Eduard Militaru, Unsplash</em></figcaption></figure><p>It’s been a year. I am tired. And I’m sure that you, dear reader, are tired too.</p><p>We’ve been designing, coding, engineering, and working our way through a global pandemic. Some of us have lost jobs, some of us have burned out, and some of us have lost friends and family.<strong> I’m here to tell you to take a step back, breathe, and know that you are seen.</strong></p><p>We’ve been thrust in an environment where, after a year of working and learning remotely, the lines between work, family, and yourself have already merged in to one. We’re in an environment where we’re expected to excel at work and be grateful that we still have a job. Although some of us are starting to see light at the end of the tunnel, a lot of us are feeling the threat of COVID-19 closing in on our personal networks.</p><p>Day after day, we see ourselves still persevering, surviving despite everything that has happened. After all, your startup just got funded. Sales are at a record high. You just snagged that promotion. You aced that interview for an opportunity abroad.</p><p>But the reality is that nothing is okay. We have all been affected by this pandemic in one way or another and its important for you to know that you are not the only one. I am not here to inspire you to pick yourself up and hustle your way to a better future. You and I know that that’s bullshit. I’m here to let you know that it’s okay to not be at your best right now. It’s okay to sleep in during the weekends. It’s okay to close your work apps and keep playing video games until midnight. It’s okay to be vulnerable and to stray from your brand.</p><p>We all have our own little ways of surviving this pandemic. What’s important is that you let yourself rest.</p><p>The grind and the hustle can and should wait. <strong>Take care of yourself first.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=764da551da17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conversational assistants in the time of Coronavirus]]></title>
            <link>https://uxdesign.cc/conversational-assistants-in-the-time-of-coronavirus-3d5cd1d5bba?source=rss-fbd130e11e32------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d5cd1d5bba</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <dc:creator><![CDATA[Richard Parayno]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 15:54:47 GMT</pubDate>
            <atom:updated>2020-05-01T11:18:04.993Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*jsgFEOU5N2zKoDb2" /><figcaption>Photo by JESHOOTS.com (@ jeshoots) on Unsplash</figcaption></figure><p>As another week of social distancing and quarantine lockdowns pass because of the COVID-19 pandemic, we’re seeing more companies go through Digital Transformation and changing the way they work. One of the digital technologies that businesses can use to cope up with the effects of the COVID-19 Pandemic is the use of <strong>Conversational Assistants</strong>. In particular, Customer Support is one of the business functions now being augmented by Conversational Assistants. With this technology, businesses can instantly respond to Frequently Asked Questions (FAQs), only forwarding their concerns to a live agent when its required.</p><p>Because of COVID-19, technology companies are forced to rethink how Conversational Assistants are created. In the past, this technology was generally more “robotic” than human. Nowadays, we see Conversational Assistants become part of larger, end-to-end systems and begin to integrate <a href="https://uxdesign.cc/leveling-up-your-chatbots-with-conversation-design-5e34cf5f3ac">Conversation Design principles</a> to create human-computer teams that are meant to augment existing processes, instead of bogging them down and trying to replace them.</p><h4>What’s the difference between a Conversational Assistant and a Chatbot?</h4><p>A Conversational Assistant is a chat or voice assistant that is meant to enhance, rather than replace the skills and functions of the person it’s assisting. <strong>It does not replace the job of the person. Rather, it creates opportunities for the person to make better use of their time and skills. </strong>On the other hand, a Chatbot is a chat or voice assistant that only does what it’s programmed to do, often without considering how a user will use it.</p><p>In general, the difference between Conversational Assistants and Chatbots is that Conversational Assistants have traits such as:</p><ul><li>Naturally communicating with the user</li><li>Avoiding using long messages, jargon, and technical terms</li><li>Understanding the user’s intent without the user explicitly saying what they want to achieve.</li></ul><p>While Chatbots usually have traits such as:</p><ul><li>Limiting the user to pre-defined choices to progress the flow</li><li>Using technical terms and unnatural responses (for example, saying “type 1 if you want to do this”)</li><li>Not taking advantage of the chat format by putting large amounts of information in one message</li></ul><p>For example, when it comes to Customer Support, a Conversational Assistant can automatically respond to FAQs, and once the Assistant encounters a question that isn’t in the FAQs, a live agent is then brought in to provide their expertise. This is what sets apart regular Chatbots from Conversational Assistants. <strong>Conversational Assistants are complete, end-to-end systems that are meant to enhance how people work, instead of just automatically replying to messages.</strong></p><h4>How can businesses leverage Conversational Assistants in a post COVID-19 world?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*C7brEl9wFCCDyqkJ" /><figcaption>Photo by Jordan Hopkins(@ jhopkinswriting) on Unsplash</figcaption></figure><p>Businesses stand a lot to gain from considering Conversational Assistants in their Digital Transformation strategies. Right now, Conversational Assistants shine the most for use cases that deal with a lot of repeatable information, such as answering customer inquiries, or easily collecting information at scale.</p><p>Industries that can do e-commerce can take advantage of Conversational Assistants by (1) automating customer inquiries on their current inventory, and (2) automatically collecting customer order information for live agents to handle the fulfillment process.</p><p>Companies operating with lean resources can leverage Conversational Assistants to collect and process information from their employees at scale. This can be helpful in, for example, running targeted surveys without using up too much of the HR team’s time.</p><p>These are just some of the examples of how businesses can use Conversational Assistants in enhancing existing workflows. <strong>However, it is not a silver bullet. </strong>Conversational Assistants cannot replace work that needs a human response, such as telemedicine and therapy. In industries where a timely human response is needed, Conversational Assistants might cause more problems than it solves.</p><h4>Closing thoughts</h4><p>As with any technology, the best thing to do is to honestly assess whether it provides value to you. Just because it’s a shiny new technology, doesn’t mean you need to use it. On the other hand, just because what you’re using now is perfectly fine, doesn’t mean that you shouldn’t find ways to improve the way you work. Digital Transformation is a continuous process, not a one time thing.</p><p>In a post COVID-19 world, businesses that successfully transition to digital, and responsibly maximize the technology that comes with it, will no doubt become the leaders of the industry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d5cd1d5bba" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/conversational-assistants-in-the-time-of-coronavirus-3d5cd1d5bba">Conversational assistants in the time of Coronavirus</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Organizing a Fully Remote Tech Meetup from your Bedroom]]></title>
            <link>https://medium.com/philippine-web-designers/organizing-a-fully-remote-tech-meetup-from-your-bedroom-d2c6e9c90003?source=rss-fbd130e11e32------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2c6e9c90003</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[live-streaming]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Richard Parayno]]></dc:creator>
            <pubDate>Sat, 04 Apr 2020 10:56:30 GMT</pubDate>
            <atom:updated>2020-04-04T10:56:30.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_51pKM8ICpLbLSzd0fa4-g.png" /><figcaption>Some of the participants of <a href="http://pwdo.org/">PWDO</a> and <a href="http://uxph.org/">UXPH’s</a> first fully remote meetup, RemoteFFC #1: Enhanced Work from Home.</figcaption></figure><p>With everyone around the world practicing Social Distancing because of the COVID-19 Pandemic, doing things remotely is now the new normal.</p><p>In particular, tech communities have started shifting to online events, workshops, and conferences. Tools such as Google Hangouts and Zoom saw a sudden increase of users as more and more people begin to rely on these tools to communicate with their friends, families, and co-workers.</p><p>On April 3, 2020, the Philippine Web Designers Organization and User Experience Philippines successfully pulled off a fully remote meetup on Zoom and YouTube Live.</p><p>Here’s how we did it, and how you can do it too.</p><h4>Why Zoom and YouTube Live?</h4><p>Before we get into the technical stuff, I’m going to share the process on how we chose the tools we used.</p><p>For context, we wanted to be <strong>inclusive</strong> and give our participants <strong>choices</strong> on how and where they could participate in the event. We held the meetup in two different channels, Zoom and YouTube Live, with Zoom being the main venue.</p><p>Zoom and YouTube Live were the chosen platforms based on the following criteria:</p><ol><li>Ease of Use and Accessibility</li><li>Admin/Room Management Controls</li></ol><p>Prior to the event, our team compared both Google Hangouts and Zoom in terms of features. Though Google Hangouts was free and (arguably) more secure, <strong>Zoom provided more comprehensive controls in terms of limiting what the participants can, and cannot do</strong>. One of the controls that we liked in particularly is Zoom’s Waiting Room feature, which allowed the organizing team to meet and set up everything before admitting people inside the room and going live (an ingress, in events management terms).</p><p>Aside from organizing the meetup in Zoom, we also set up a stream of the meetup on YouTube Live. In the past, we used Facebook Live as our livestream platform of choice. <strong>However, we recognized that not everyone wants to use their Facebook account and expose their personal information just to attend a meetup.</strong></p><p>Our team decided that out of the two choices (Facebook and YouTube), YouTube was the better option. Our decision paid off too, because YouTube was faster and easier to set up compared to the sluggish and hacky experience you get when you stream on Facebook Live (if you’ve ever tried to connect OBS to Facebook Live, you’ll know what I mean).</p><h4>What do you need to run a fully remote meetup?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*46P1pQSzBIKInJs1PMb_SQ.png" /><figcaption>Behind-the-scenes of the setup I used to keep everything moving smoothly.</figcaption></figure><p>With money being tight, we need to make the most out of what we have.</p><p>Before planning the remote meetup, make sure to prepare the following things:</p><ul><li>Devices for streaming</li><li>Zoom Pro Subscription</li><li>Well defined roles of the Organizing team</li><li>Event Script and Pre-Recorded Speaker Talks (more on this later)</li></ul><p>The stream set up was comprised of three devices, a desktop computer for streaming the Zoom room and the talks to YouTube, a laptop for screensharing the talks to the Zoom room, and a phone for communicating with everyone on the organizing team.</p><p>In terms of software, we used the free version of <strong>Streamlabs OBS</strong>. I liked how easy it was to set up and connect to our YouTube channel, and how easy it was to integrate donations to our stream.</p><h4>Do you need a powerful or sophisticated computer to livestream a meetup?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pf0p9vNx65r6CUV3VMpF8w.png" /><figcaption>This is what my set up of Streamlabs OBS looks like.</figcaption></figure><p><strong>No.</strong> In a previous meetup, I was able to livestream with just my Macbook Pro Late 2016. In my experience, the most important things you need to stream an event are the following:</p><ol><li>A good, stable internet connection and enough RAM and CPU power to keep things from stuttering (especially if you’re streaming and hosting the meetup on only 1 device).</li><li>Good and well thought out topics for the meetup.</li></ol><p>For context, my desktop computer’s processor was a Ryzen 5 1500x, which was more than enough for the type of content that we were going to stream. I also had the privilege of having a 50mbps Fiber connection at home.</p><h4>How did you facilitate everything?</h4><p>The biggest challenge in organizing a remote meetup is making sure everything runs smoothly.</p><p>Being in the Philippines, it’s a given that not everyone’s internet connections will be great. A lot of us here are not privileged to have access to Fiber internet or even stable 4G/LTE data.</p><p>To reduce the number of things that could potentially go wrong during the meetup, <strong>we asked the speakers to pre-record their talks. </strong>However, this came with it’s own set of challenges:</p><ol><li>How do we show the pre-recorded videos on the YouTube stream?</li><li>How do we show the pre-recorded videos in the Zoom room?</li></ol><p>After experimenting with our options during our test stream, we settled on the following:</p><ol><li>For the YouTube Stream: In <strong>Streamlabs OBS</strong>, We put each speaker’s talk in their own Scenes, and made separate <strong>Media Sources</strong> for the video files of their talks. This allowed us to share a high-definition copy of their talks with no delays.</li><li>For the Zoom room: Since we were on video conferencing software, we accepted the fact that everything we do to display the speaker talks will have some sort of delay. We settled on screensharing the videos that the speakers sent. <strong>With this method, there was a slight drop in framerate in the videos, but the sound was still the same. </strong>In our experience, the bandwidth usage of Zoom was lower for the end user compared to YouTube Live. The tradeoff was well worth it for those in Zoom.</li></ol><p>Technical details aside, another important aspect of successfully facilitating a remote meetup is a strong, well-organized team.</p><p>For the meetup, we identified the following roles that the people would be doing:</p><ol><li><strong>Stream Master/Stream Pilot: </strong>The Stream Master or Stream Pilot is the person who will be in charge of managing the stream, timing the transitions, and playing the speaker videos. In our case, this was me because I had access to stable Fiber internet and had a desktop that could handle streaming while multitasking.</li><li><strong>Meetup Host: </strong>The meetup host is the person who engages with the audience, whether its in YouTube or Zoom. They’re also the one in charge of facilitating the Q&amp;A sessions and panel discussions, as well as making sure the program flow is strictly followed.</li><li><strong>Zoom/YouTube Moderators: </strong>The Zoom and YouTube moderators would be the one watching over the chatrooms for potential issues, complaints, and violations of our Codes of Conduct. They would also be the ones in charge of blasting announcements to the participants in the chatrooms, such as donation links and other relevant information.</li></ol><p>If you’re coming from an environment of physical meetups, you’ll be surprised to see how many of the roles in those meetups translate to remote meetups.</p><h4>Insights and Closing Thoughts</h4><p>For both PWDO and UXPH, we were used to holding large scale, in-person events. We’ve livestreamed some of our events before, but doing a fully-remote event was new territory for both of our orgs.</p><p>After the meetup, we’ve learned the following things:</p><ul><li><strong>Our audience was more engaged both in YouTube and Zoom compared to our previous meetups.</strong> We think that communicating through a chatroom is less awkward for most people.</li><li><strong>We were able to retain a stable attendee count throughout the entire event. </strong>For context, we released a total of 80 tickets on Eventbrite, and we got 50 participants in Zoom and 20 participants in YouTube live. <strong>This figure stayed the same despite starting the meetup late and ending it late.</strong></li><li><strong>The COVID-19 Pandemic shouldn’t prevent us from creating quality events for our communities. </strong>As tech communities, we shouldn’t let this pandemic let us down. We should continue to innovate and find ways for us to share knowledge to each other in the community.</li></ul><p>Will we ever do a remote meetup again?</p><p>The answer is yes. This was a great experience for everyone involved, and it allowed us to explore a new, more inclusive meetup venue for everyone.</p><p><em>If you want to read or see a more in-depth guide on how you can set up your streaming environment, let me know by clapping for this article and sharing it to all your friends! If you want to see the end result of our livestream, you can see it here at: </em><a href="https://youtu.be/-amLnZxpDEA"><em>https://youtu.be/-amLnZxpDEA</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2c6e9c90003" width="1" height="1" alt=""><hr><p><a href="https://medium.com/philippine-web-designers/organizing-a-fully-remote-tech-meetup-from-your-bedroom-d2c6e9c90003">Organizing a Fully Remote Tech Meetup from your Bedroom</a> was originally published in <a href="https://medium.com/philippine-web-designers">Philippine Web Designers Organization</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Old Meets New: A Recap of the PH Tech Leads 2020 Kickoff]]></title>
            <link>https://medium.com/philippine-web-designers/when-old-meets-new-a-recap-of-the-ph-tech-leads-2020-kickoff-cd17c6e2cca7?source=rss-fbd130e11e32------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd17c6e2cca7</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[philippines]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Richard Parayno]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 05:15:53 GMT</pubDate>
            <atom:updated>2020-01-20T05:15:53.613Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cBaYhsKqYNMCwrezq4e3LA.png" /><figcaption>Meet the PH Tech Community Leaders for 2020.</figcaption></figure><p>On January 9, 2020, old and new leaders of the Philippine Tech Community gathered at the BHP office to formally kickoff the new year.</p><p>The meetup was officially started by <strong>Ms. Jen Borlaza (BHP)</strong> with a quick introduction to BHP (Broken Hill Propriety), a leading global resources company, with interests in the minerals, oil, and gas industries. Ms. Jen, manages end-to-end resources and on-boarding of talents in BHP, shared to the attendees what their Manila office does, and how the venue partnership came to be.</p><h3>Icebreakers and Introductions</h3><p>Moving forward, <strong>Kit Valmadrid</strong> <strong>(PWDO)</strong> took the stage and started off the round of introductions around the room. Tech Community leaders, both old and new, introduced themselves, their communities, and what they do in their community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*09rg40UnTsSZsHQte1uqQw.png" /><figcaption>Kit Valmadrid and Pierce Jonota from the Philippine Web Designers Organization (PWDO) hosted the meetup.</figcaption></figure><p>After the round of introductions, attendees were treated to dinner by BHP, the venue and food sponsor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*JMNf-_WDL8FucExGGCcAeg.png" /><figcaption>A peek at the delicious food served during the evening.</figcaption></figure><h3>Welcoming the New Generation of Leaders</h3><p>As everyone was settling down in the venue after dinner, new leaders and communities were welcomed to the PH Tech Leads Community. Communities such as<strong> GoManila</strong>, <a href="http://wi-tech.org/"><strong>WiTech</strong></a><strong>, WikiSocPH, and </strong><a href="http://gdgcloudmanila.org/"><strong>GDG Cloud Manila</strong></a><strong> </strong>were formally vouched to the PH Tech Community. New leaders such as <strong>Richard Parayno (PWDO), Audrey Pe (WiTech), Mae Gallos (GoManila), Brian Tan Seng (GDG Cloud Manila), and Monina Maturan (Salesforce Community Philippines — Women in Tech) </strong>were also formally vouched to the community.</p><h3>Collaborating on the Community Calendar</h3><p>Next on the agenda was the plotting of dates of major activities of the different tech communities in attendance. Flagship community events such as <strong>DevCon Summit</strong>, <strong>HackReality</strong>, <strong>UXPH Roadshow</strong> and <strong>Junior Form Function &amp; Class</strong> reserved their slot on the <a href="https://www.phtechcommunity.org/events/">community calendar</a> to ensure that there are no conflicts for the benefit of the organizers and the communities themselves. The community calendar is an initiative started by the PH Tech Community Leads for everyone to align and support each other’s projects. Communities are <em>highly encouraged</em> to create accounts on the PH Tech Community website and upload their events there. Notably, the communities were given a large chunk of time during the meetup to plot important events and to provide Sponsorship Primers since <strong>Haifa Carina</strong> <strong>(DevCon)</strong> would be forwarding these to potential sponsors for everyone’s benefit. Ample time was also given to align the monthly hosts and discuss the hosting guidelines for the PH Tech Community meetups.</p><h3>Reviewing Policies and Guidelines</h3><p>Aside from working on the community calendar, membership guidelines and criteria were also revisited to account for recent changes in the tech community. Specifically, the policy on students being part of the PH Tech Community Leads was revisited as we are seeing students stepping up and leading organizations that serve not only students, but professionals as well. Due to lack of time and the complexity of the topic, the tech leads settled on the following criteria for membership into the PH Tech Community Leads:</p><ul><li>The organization <strong>must not </strong>be school based.</li><li>The organization <strong>must </strong>be professional-led.</li><li>The organization <strong>must </strong>be a non-profit.</li><li>The organization <strong>must </strong>be enthusiast-driven or volunteer-led.</li></ul><p>It was then mentioned that the PH Tech Community Leads would maintain two directories, one containing <strong>active member communities</strong>, and another containing <strong>inactive member communities.</strong> This would be for highlighting which communities are currently active, while not forgetting to acknowledge the communities that have been members in the past.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*tpeFyIllq14Fcytcxu-RPw.png" /><figcaption>Community leaders Kit Valmadrid (PWDO) and Michie Ang (WWCode Manila, SwiftPH) exchanging ideas to improve the community policy.</figcaption></figure><h3>One Platform to Rule Them All</h3><p>Later on in the evening, the topic of using a single platform for PH Tech Community Lead Meetups was raised. The main concern shared by the tech community leads is that they want to move away from Facebook events as much as possible. After much discussion about potential platforms used by the different communities, it was agreed upon that for Q1, <a href="https://www.meetup.com/">Meetup</a> would be used as the Event RSVP Platform. For Q2, it was agreed upon that it would be the host organization’s decision what Event RSVP Platform to use, as long as it is inclusive for all of the tech communities needs. These Event RSVP Platforms would then be evaluated by the communities by midyear to see which one worked for everyone.</p><p>After the main agenda was tackled, there was a quick, open discussion on what kind of topics could be discussed in the PH Tech Community meetups. Some of the suggested topics were:</p><ul><li>SEC Registration</li><li>War Stories and Wow Stories</li><li>Capacity Planning</li><li>Sponsorships</li></ul><p>As the night winded down, the tech community leads then gathered for a class photo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*M7msOOGeyF_SmR3ekr9VhQ.png" /></figure><p>Notably, this would be the last PH Tech Leads Meetup that <strong>Jordan Deja (UXPH)</strong> and <strong>Kit Valmadrid (PWDO)</strong> attend as active members for a while, as they attend to other things with their lives. We wish them all success in their future endeavors.</p><h3>A Surprise From AWS</h3><p>Before the night ended, attendees were surprised by Amazon Web Services with free AWS hoodies for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*F4nZ1Iqcb8omckdscritKw.png" /><figcaption>Amazon Web Services were also present at the kickoff and provided attendees with free hoodies!</figcaption></figure><h3>Insights of a Freshman Community Leader</h3><p>In attendance for the evening was a total of <strong>33 community leaders, with 22 tech communities represented. </strong>The PH Tech Community is growing day by day, and we’re currently experiencing a massive shift in leadership as communities begin passing the torch to the younger generations. Exciting times are on the horizon as well, as we see communities bringing their events to malls, organizing bigger, more diverse and inclusive conferences, and even bringing their flagship events to places outside of Metro Manila.</p><p>There is no better time than now to collaborate and share with each other our knowledge in managing communities. The past decade saw our communities laying the building blocks of what we have right now. The next decade should be, in my opinion, where we go farther and higher than we have ever been, for the betterment of our communities, ourselves, and most importantly our country.</p><p>When old meets new, who knows how far we can go?</p><p><em>If you are a tech community interested in joining the PH Tech Community Leads, you may contact Haifa Carina of DevCon or Bob Reyes of Mozilla Philippines through the </em><a href="https://www.phtechcommunity.org/contact/"><em>PH Tech Community Contact Form</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd17c6e2cca7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/philippine-web-designers/when-old-meets-new-a-recap-of-the-ph-tech-leads-2020-kickoff-cd17c6e2cca7">When Old Meets New: A Recap of the PH Tech Leads 2020 Kickoff</a> was originally published in <a href="https://medium.com/philippine-web-designers">Philippine Web Designers Organization</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveling up your chatbots with conversation design]]></title>
            <link>https://uxdesign.cc/leveling-up-your-chatbots-with-conversation-design-5e34cf5f3ac?source=rss-fbd130e11e32------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e34cf5f3ac</guid>
            <category><![CDATA[conversation-design]]></category>
            <category><![CDATA[conversational-interfaces]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Richard Parayno]]></dc:creator>
            <pubDate>Thu, 07 Nov 2019 12:12:20 GMT</pubDate>
            <atom:updated>2019-11-11T18:40:07.885Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article is based on my talk last October 16, 2019 for the </em><a href="https://medium.com/u/988763967039"><em>Philippine Web Designers Organization</em></a><em>’s MiniFFC#56: Unconventional Design Meetup held at Proudcloud HQ in Quezon City, Philippines.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZMLixiBXa0dbntBqoD3Xjw.png" /></figure><h3><strong>Hello, Internet! 👋</strong></h3><p>I’m Richard, a Conversation and User Experience Designer working at <a href="https://senti.ai/">Senti AI</a>, the pioneering AI company in the Philippines. I’m an active volunteer in local tech communities such as the <a href="https://pwdo.org/">Philippine Web Designers Organization</a> and <a href="https://uxph.org/">UX Philippines</a>. I’m usually part of the many teams that move behind the scenes in the Philippine Tech Community. Now, it’s my turn to share some insightful content for you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*CXCPLcGosWHckE7NRX2v8w.jpeg" /><figcaption>This was my first talk about UX that was tailored for professionals!</figcaption></figure><p>I’ve been working as UX Designer for almost a year now. Working at an AI company, I was constantly exposed to tech that is augmented by Artificial Intelligence and Machine Learning. This environment lead me to explore areas where I could apply UX in AI such as <em>Conversation Design.</em></p><h3>What is Conversation Design? 🤯</h3><p>According to <a href="https://designguidelines.withgoogle.com/conversation/conversation-design/welcome.html#">Google’s Conversation Design Guidelines,</a> Conversation Design is a <em>design language</em> based on human conversation.</p><p>Being a <em>design language</em>, you can apply it anywhere you want. You can use Conversation Design to make your web or mobile application’s interfaces more <em>conversational</em>! ✨</p><p>In this post though, we’ll be focusing on applying Conversation Design on where it really shines right now — designing Chatbots!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_sgGeGY4X6U3spUSMoxGQ.png" /><figcaption>Chatbots and You are 💙!</figcaption></figure><h3>I want to get started with Conversation Design. Where do I start?</h3><p>Just like other specializations in the umbrella of UX, there are some things that you need before you get started.</p><h4>1. A firm grasp on the UX Design Process.</h4><p>In Conversation Design, it’s very important that you have a firm grasp on the UX Design Process because you will constantly be going through that process as you design conversations. You need to be comfortable with doing User Interviews, Contextual Inquiry, Rapid Prototyping, Usability Testing and constant iteration.</p><p>If you don’t have a firm grasp on the design process but you want to start in Conversation Design, be prepared to exert double effort. Not taking into account the UX Design Process will result in a chatbot that does not create value for the user, even if conversing with the Chatbot feels natural for the user.</p><h4>2. Decent Communication Skills</h4><p>You need to have decent communication skills if you want to do Conversation Design. You don’t need to have written an article before or spoken in front of a crowd. All you need is to be able to carry a conversation with another person naturally, regardless of your language.</p><p>If you are not a good communicator, it will reflect on your Chatbot, and the experience won’t be good for the user. The secret to good Conversation Design is pretty much just sticking to how we normally communicate as humans, with all our quirks and nuances.</p><h4>3. Familiarization with The Cooperative Principle (or Grice’s Maxims)</h4><p>The Cooperative Principle (also referred to as Grice’s Maxims) are taken from the social sciences, specifically linguistics. The Cooperative Principle is a set of principles <strong>observed by humans </strong>when engaging in <strong>efficient communication</strong>. Considering these principles when doing Conversation Design is <strong>essential </strong>to creating conversational interfaces. This will be discussed later in the article.</p><p>The Principles, if not applied to your designs, would result in a conversation that feels robotic and forced.</p><h3>Cool! How is The Cooperative Principle essential to Conversation Design? 👀</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jAjSx_4LJMOobchi0Yiwiw.png" /></figure><p>With The Cooperative Principle, Paul Grice was able to describe how humans communicate efficiently in normal, everyday situations. The overall concept of The Cooperative Principle is that when humans communicate, the participants will instinctively cooperate with one another. However, due to the quirks of human conversation (such as saying something that isn’t entirely truthful), these maxims should be looked at examples of ideal conversation.</p><h4>1. Maxim of Quality</h4><p><em>“We instinctively cooperate </em><strong><em>in terms of the truth of what we say.</em></strong><em>”</em></p><p>As humans, we naturally want to have a truthful conversation with whoever we’re talking to. The Maxim of Quality states that whenever we converse with another person, we should state things that are genuine and true.</p><blockquote><strong>Correct Example:</strong></blockquote><blockquote>Person A: “Hey Richard, have you finished the screens for the Account Creation Flow?”</blockquote><blockquote>Person B: “Not yet, but they should be ready 2 days from now.”</blockquote><blockquote><strong>Wrong Example:</strong></blockquote><blockquote>Person A: “Hey Richard, have you finished the screens for the Account Creation Flow?”</blockquote><blockquote>Person B (lying): “Yup! I actually already sent it to you a week ago. It must’ve been sent to your spam inbox.”</blockquote><p>In Conversation Design, we can apply the Maxim of Quality by making sure that our bot isn’t saying any wrong information. The most important thing to remember with the Maxim of Quality is that our chatbot should always be truthful, and should not be spreading false information.</p><h4>2. Maxim of Quantity</h4><p><em>“We instinctively cooperate </em><strong><em>in terms of</em></strong><em> </em><strong><em>the quantity of information that we provide.</em></strong><em>”</em></p><p>The Maxim of Quantity states that we cooperate based on how much information that we give and receive in a single exchange. In an ideal situation, we answer questions directly and avoid adding irrelevant information.</p><blockquote><strong>Correct Example:</strong></blockquote><blockquote>Person A: “What are you going to do tonight?”</blockquote><blockquote>Person B: “I’m just going to stay in and watch Netflix.”</blockquote><blockquote><strong>Wrong Example:</strong></blockquote><blockquote>Person A: “What are you going to do tonight?”</blockquote><blockquote>Person B: “I have a dentist’s appointment later, but probably I’m going to watch Netflix tonight. Do you want to go with me?”</blockquote><p>We can apply the Maxim of Quantity to our Chatbots by making sure that we respond to what the user asks, and not adding any fluff. Chatbots should communicate to the user directly and answer what the user asked. This is to better guide the user in the conversation and to reduce the chance of error.</p><h4>3. Maxim of Relevance</h4><p><em>“We instinctively cooperate </em><strong><em>in terms of the relevance of what we contribute.</em></strong><em>”</em></p><p>The simplest of all the Maxims, the Maxim of Relevance states that what we say must be relevant to the conversation.</p><blockquote><strong>Correct Example:</strong></blockquote><blockquote>Person A: “Have you seen my phone? I swear I placed it here earlier.”</blockquote><blockquote>Person B: “Yeah, you actually left it in the bathroom.”</blockquote><blockquote><strong>Wrong Example:</strong></blockquote><blockquote>Person A: “Have you seen my phone? I swear I placed it here earlier.”</blockquote><blockquote>Person B: “I can’t find mine either.”</blockquote><p>The Maxim of Relevance can be applied to our chatbots by making sure that what our chatbots say are relevant to the conversation and actually answer what the user asked.</p><h4>4. Maxim of Manner</h4><p><em>“We instinctively cooperate </em><strong><em>in terms of the way we strive to communicate clearly, without obscurity or ambiguity.</em></strong><em>”</em></p><p>Lastly, the Maxim of Manner states that we should communicate in an orderly fashion, where every detail is clear and nothing is confusing to the user.</p><blockquote><strong>Correct Example:</strong></blockquote><blockquote>Person A: “What were you up to before we met up today?”</blockquote><blockquote>Person B: “I decided to have a chill morning and drink some coffee first before going here.”</blockquote><blockquote><strong>Wrong Example:</strong></blockquote><blockquote>Person A: “What were you up to before we met up today?”</blockquote><blockquote>Person B: “I got a cup of coffee at the coffee shop but I forgot to get my keys at the apartment so I had to go back there first and finish my coffee.”</blockquote><p>Applying this to Chatbots can be as simple as making sure that what our Chatbots says makes sense logically. This is crucial in conversations where we have to outline steps to our users, such as how they can avail a promotion for a product or how they can open an account.</p><h3>How is The Cooperative Principle applied in Chatbots? 🤔</h3><p>Let’s dive into some sample conversational flows and see how we can apply the Cooperative Principle.</p><h4>Example 1 — Phone Store Chatbot</h4><p>Let’s say we have a chatbot for a physical store that sells phones. In this scenario, Richard is looking for a flagship android phone and decides to message their Facebook page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UDoPXwH2Diu38wpdUGlzgg.png" /></figure><p>If the Phone Store got an off-the-shelf chatbot without first considering the design of the conversations, this is one of the scenarios that can happen. Instead of picking up Richard’s request of <strong>flagship</strong> android phones on sale, the chatbot responded generically and repeated what Richard just said. Keeping in mind the Cooperative Principle, making users repeat what they just said doesn’t make the conversation flow naturally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xrfjxSw4VFj4ZzdaVsNK1w.png" /></figure><p>Improving upon the previous example, we can see here that the Chatbot responds in such a way that it acknowledges what Richard said. This conversational flow, compared to the previous example, sounds like what an actual salesperson in a phone store would say. The change in how the Chatbot treats the user as a participant in a conversation (compared to using canned responses) can make all the difference in engaging your users.</p><h4>Example 2 — Chatty Customers</h4><p>Let’s say that we have the same Phone Store Chatbot. This time, with a particularly chatty customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5swHyA60TgJQGQygHgfLpA.png" /></figure><p>In this example, Richard added an unrelated follow up statement (or <em>intents</em> as they are called in Conversation Design) to what he previously told the bot. Normally, the default behavior of Chatbots are to state that they don’t understand the statement and would ask the user to repeat what they said in an effort to reset the conversation. With this conversational flow, it makes it seem like the Chatbot is either broken or not really equipped to converse with actual users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JoHqW2EDdubEcJpxA3lkA.png" /></figure><p>Observing The Cooperative Principle and applying Conversation Design to the previous example, we can see here that the Chatbot is able to detect the change in statement or intent of the user. This small change improves the overall user experience greatly, with the Chatbot seemingly able to listen to an actual user. For the user, this would improve engagement and make them keep using the chatbot since they know that it provides value to them as a customer.</p><p>Always keep the Cooperative Principle in mind when you’re designing conversations. The four principles will help you in making your Chatbots more <em>conversational</em>, more <em>useful</em>, and a little more <em>human</em>.</p><h3>Why Chatbots? 🤖</h3><p>I chose to study on Conversation Design because Chatbots are starting to pop up everywhere in our daily lives. If you step back and assess all of the technology that you’re using now, you would be surprised how much we interact with Chatbots on an everyday basis. From our favorite digital wallets and payment apps, to Facebook Pages that instantly reply to your questions.</p><p>However, as technology becomes more ubiquitous, there is a tendency to maximize it by offloading repetitious tasks to machines, robots, or computers in general.</p><p>Conversation Design plays a huge role in developing chat and voice assistants because we as humans have a tendency to create responses that <em>sometimes</em> sound like robots. It’s a common pitfall for us to think sequentially and forget to consider the nuances of human conversation in our products. Little things that we take for granted such as suggesting to the user what they could do with the product gets lost as we build AI-powered Chat Assistants and, in general, pursue technology that is enabled by Artificial Intelligence.</p><p>As a Conversation Designer, your job would be to step back, assess the entire conversational flow, and ask yourself, “Is this how I would talk to another person?”.</p><h3>Whew! That was a lot to take in! 😬</h3><p>There definitely were a lot of terms, jargon, and overall a different style of designing products listed in the article. It may not be much, but what you’ve just read is enough for you to understand the role of Conversation Design in creating Chatbots and see how theory can be put into practice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSwCyz9aOyZhyczzKfr%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FSwCyz9aOyZhyczzKfr%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExaGM1cjBhMnZkbnd6czBnM253eWQ0eHBuYW81eW9qcm54anJjcmEwMCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FSwCyz9aOyZhyczzKfr%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/94b4f4761ca8cdd82e7d84bf56b9f7b5/href">https://medium.com/media/94b4f4761ca8cdd82e7d84bf56b9f7b5/href</a></iframe><p>With that, you’re now ready to level up your Chatbots and create valuable AI-powered chat assistants that you can talk to like a human.</p><p>Before I finish the article though, there are a few things that I want you to remember as a Conversation Designer:</p><h4>Intelligent Assistants are everywhere.</h4><p>Voice and Chat Assistants are everywhere now, and we can expect more assistants to pop up as ML technology improves. The more Chatbots get pushed to the market, the more important it is to consider Conversation Design. <strong>It is our job as Conversation Designers to help people accept Chatbots (and AI in general) and help them see how their lives can be improved with this technology.</strong></p><h4>Too much tech is being introduced that creates more problems than it solves.</h4><p>There was a Chatbot I used before that the company used as their primary customer support. It’s a great idea, for sure, but the minute I asked a question that (I assume) wasn’t part of the canned responses, the Chatbot just straight up didn’t respond to me anymore. This just frustrated me because I was really having problems with their product and I couldn’t use it normally. <strong>As Conversation Designers working on Voice and Chat Assistants, the responsibility is on us to make sure that the people who use our products have a delightful and valuable experience.</strong></p><h4>As we innovate, we sometimes forget the human element.</h4><p>This is especially true when we further push the envelope of technology through Artificial Intelligence and Machine Learning. We become so absorbed in creating the next big product or become the next big unicorn that we forget that ultimately, us humans are going to be using the very same products that we build. We should strive to make delightful experiences not only for us, but also for the people building the product, for your parents, for your friends, and for humanity as a whole. Because its not your computer that’s going to be affected when a product isn’t designed properly. <strong>It’s going to be you.</strong></p><p><em>This was my first blog post ever! I hope you learned something as I did when I wrote this. Did you love it or hate it? Comments on the content and how to improve my writing are very much appreciated!</em></p><p><em>LinkedIn</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e34cf5f3ac" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/leveling-up-your-chatbots-with-conversation-design-5e34cf5f3ac">Leveling up your chatbots with conversation design</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>