<?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 Alexander Adamyan on Medium]]></title>
        <description><![CDATA[Stories by Alexander Adamyan on Medium]]></description>
        <link>https://medium.com/@alexadamyan?source=rss-50d2751ed15b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*wyzrMeJd4xNCF5wBE3AF_A.jpeg</url>
            <title>Stories by Alexander Adamyan on Medium</title>
            <link>https://medium.com/@alexadamyan?source=rss-50d2751ed15b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:27:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexadamyan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Trials and Tribulations of Building a Great Team | Salon Owner’s Guide]]></title>
            <link>https://medium.com/retentionforce/salon-and-spa-staff-management-a8ea63921ead?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8ea63921ead</guid>
            <category><![CDATA[salon-business]]></category>
            <category><![CDATA[salon-and-spa]]></category>
            <category><![CDATA[salon-management]]></category>
            <category><![CDATA[staff-management]]></category>
            <category><![CDATA[staffing-and-recruiting]]></category>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 13:58:49 GMT</pubDate>
            <atom:updated>2020-05-08T23:24:21.495Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Trials and Tribulations of Building a Great Team | The Salon Owner’s Guide</h3><p>Anyone who has ever owned or managed a salon knows that sometimes, finding and managing staff is about as easy as herding cats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/0*E5dhi6s7D9w8fTTD" /></figure><p>In fact, many salon owners say it’s their number one problem.</p><p>From finding the right people, paying the right wages and setting the right commission, to motivating everyone to all get along and work together, it’s not surprising that it’s a challenge that leaves many business owners tearing out their hair. 😱</p><p>But, help is at hand. Here, we’ll take a look at the steps you can take to make your hiring and day-to-day staff issues more straightforward.</p><blockquote>Here’s how to get it right:</blockquote><h4>Read more:</h4><p><a href="https://www.retentionforce.com/articles/salon-recruitment-guide-step-by-step-or-salon-owners-guide/">https://www.retentionforce.com/articles/salon-recruitment-guide-step-by-step-or-salon-owners-guide/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8ea63921ead" width="1" height="1" alt=""><hr><p><a href="https://medium.com/retentionforce/salon-and-spa-staff-management-a8ea63921ead">The Trials and Tribulations of Building a Great Team | Salon Owner’s Guide</a> was originally published in <a href="https://medium.com/retentionforce">RetentionForce</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing Software Engineer Recruiting in Armenia the Right Way]]></title>
            <link>https://medium.com/itjobs-am-hiring-for-it-and-startups-in-armenia/hiring-software-engineers-in-armenia-fc7b0762882a?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc7b0762882a</guid>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 13:08:20 GMT</pubDate>
            <atom:updated>2017-10-05T05:59:57.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tz58NuOcsP278JpoZAke_Q.jpeg" /></figure><p>It’s known that there is a great demand for good software engineers around the world. Unfortunately, the demand is greater than the job market can offer. Companies will always compete for a great talent. This competition raised the software engineer salaries to the highest point that it has ever been before.</p><p>The situation in Armenia is no different. It’s even a bit worse. While there is a constant growth in a number of new tech-savvy young people, many of them become freelancers, found their startup or leave the country once they grow to a certain level. So what should be the tactics for talent acquisition in a such competitive environment?</p><blockquote>…it’s a fact that when hiring experienced software engineers it’s the employee who chooses the company not the other way around.</blockquote><p>Many of the companies we have worked with complain that they don’t receive enough number of CVs. Most of the experienced developers don’t have up-to-date CV in the first place. They just don’t need it. Because doesn’t matter if you agree with it or not, it’s a fact that when hiring experienced software engineers it’s the employee who chooses the company not the other way around.</p><blockquote>No matter how high is the demand for great talents, at the end of the day they all need some place to work</blockquote><p>That’s why many companies do headhunting and use such techniques as talent recommendation chains, or simply put — finding a candidate based on the recommendation of another talented worker that you already have. Headhunting is the last resort for the desperate employer who can’t find the right candidate through common means. So instead of investing in headhunting a company should invest in improving their image, reputation and attractiveness. No matter how high is the demand for great talents, at the end of the day they all need some place to work. To understand how engineers choose an employer you need to think like them. It’s not hard and quite predictable, and surprisingly, they <strong>don’t think much about salary</strong> at this stage. Here is a list of the most common factors software engineers consider:</p><ol><li><strong>The name, what the company does and how successful it is</strong> — is this company famous enough, cool enough and does something meaningful or not. Nobody wants to join a company that is just average. Everybody wants to be a part of something meaningful and successful. It’s not about size of the company though.</li><li><strong>The type</strong> — startups vs software development companies. It is a matter of taste and there is no good or bad. In startups engineers are usually busy with one big project and use a defined list of technologies, generally have a decision making role and should be ready to do just any task. On the other hand, in software development companies engineers usually work on many different projects with many different technologies and have less freedom in decision making. So there are people who prefer startups and there are people who prefer software development companies.</li><li><strong>The culture </strong>— is one of the most important criteria when choosing a company, though usually neglected by employers. Software engineers are looking for a friendly and welcoming environment, good leadership, growth opportunities and a place where they can have fun while working. Establishing a good corporate culture is a very difficult task.</li><li><strong>The project/role</strong> — ambitious developers are always looking for ambitious projects and “cool technologies”. They are not afraid of challenges and get bored when there is a lack of progression.</li><li><strong>What do others say about it</strong> — the reputation of your company. While you can’t change anything directly, your strategy should be to treat your employees well, organize public events, internships and trainings, sponsor and participate in the events like Barcamp, Digitec and others. Build your brand not only for your customers but also for engineers.</li></ol><h3>How to stand out?</h3><p>So in order to hire talented people your company should stand out. While there are some fundamental things in your company you might not be able to or might not want to change, there are things you actually can improve to showcase your company in a better light. Think about it exactly the same way you think about marketing. Actually it has it’s own name: <strong>HR Marketing</strong>. You <strong>should</strong> do marketing to attract the right professionals, just like you do to attract more customers. Like a sales cycle starts with prospecting, talent acquisition should start by offering something the potential candidates might want.</p><p>When creating a job announcement follow these simple tips to make sure potential candidates see your company at it’s best.</p><ul><li><strong>Be short and don’t use lengthy description</strong> — since prospects haven’t decided to apply yet they are not ready to invest time in reading your great article. Instead use short, simple messages that quickly attract attention.</li><li><strong>Showcase your office </strong>— remember that employees spend almost as much time at work as they do at home, so this makes a lot of sense. Attract great candidates with the environment they would love.</li><li><strong>List the benefits </strong>— in the job announcement don’t forget to list all benefits you offer to highlight how you’re different.</li><li><strong>Show your culture</strong> — while this is the most neglected point it has a critical priority. List your company values and the steps you take to attain them. Even if possible include quotes from your employees, let candidates see how it is to work in your company.</li><li><strong>Describe the project/role</strong>- a candidate should be able to learn about the role and the project he will be working on. You should not focus on duties and responsibilities, instead highlight why this position is so cool.</li><li><strong>Applying should be easy</strong>- stop hoping for a bunch of neatly compiled CVs. Like in the marketing, you eliminate any obstacles during the sign-up stage, the same philosophy should be used when hiring.</li></ul><h3>Conclusion</h3><p>To be successful in hiring good software engineers or just any exceptionally talented people, you should invest in HR Marketing. You need to switch the mindset and start treating potential candidates as you’re treating potential customers. Improve your company’s position and work hard to make it attractive. Your company is a product you’re selling to potential employees.</p><p>Be among the best, offer the best and the best talents will join you.</p><p>We at <a href="http://www.itjobs.am/">itjobs.am</a> believe that attracting right candidate shouldn’t be that difficult and every day we challenge ourselves to build a platform where any employer will be able to showcase their company at it’s best. And the great thing about <a href="http://www.itjobs.am/">itjobs.am</a> is that you can start using it completely free of charge.</p><p><a href="http://www.itjobs.am/employer"><strong>Sign up today</strong></a><strong> and start smart hiring</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc7b0762882a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itjobs-am-hiring-for-it-and-startups-in-armenia/hiring-software-engineers-in-armenia-fc7b0762882a">Doing Software Engineer Recruiting in Armenia the Right Way</a> was originally published in <a href="https://medium.com/itjobs-am-hiring-for-it-and-startups-in-armenia">itjobs.am — Read about Armenian IT Companies and Events</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I hate chatbots… yet still love them]]></title>
            <link>https://medium.com/research-engineering-at-simply-technologies/why-i-hate-chatbots-yet-still-love-them-521d67eb0b61?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/521d67eb0b61</guid>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <category><![CDATA[chatbot-development]]></category>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 08:36:24 GMT</pubDate>
            <atom:updated>2017-09-06T08:36:24.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1II5aGn5QedxxVat5u33gQ.jpeg" /></figure><p>What’s the hype behind chatbots? Why do we need another way of communication with a computer if we already have standard GUIs we’re all used to?</p><p>Just think about the way chatbots are used today — e-commerce for example. Buying things through chat, that’s ridiculous! Why the hell should I ask a bot to find me something if I can just search and see the list of everything I might want in a simple webpage, in a page where I can scroll, see other results, and go back and forth?</p><p>In general chatbots (like any other application) have the following workflow: collect information, perform an action and display the result.</p><h3>Chatbots collect information</h3><p>The natural way to collect information for chatbots is by asking questions, things like “What’s your name?”, or “What size pizza do you want?”. In contrast, in a form based UI there are inputs for collecting information.</p><p>Because chatbots collect information via question/answer conversation, there are number of potential issues you will need to consider when building a chatbot.</p><p><strong>Entity extraction:</strong> Entity extraction is a way for a chatbot to get meaningful information from an arbitrary text, like understanding names, dates, location, time, money, and so on. While there are plenty of ready to use tools for entity extraction from text (e.g a user’s name) you can never be 100% sure that it will work properly all the time. For example, during a previous project, we had an issue with a very common Dutch surname “<em>Van den Berg”</em>, where only “<em>Berg</em>” was recognized as a name<em>. </em>While extraction techniques are being improved and trained constantly, there will always be such a risk.</p><p><strong>Editing the data: </strong>Another challenging situation might occur with data editing, as the text the user sent has already been processed. Suppose the user misspelled his name and wants to fix it. The natural way would be to send a clarification message to the bot. Properly processing such cases might be a difficult task, but if you don’t deal with it, you might end up with something like in the picture below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lYXoglBkh7wa2G0GO_gF-A.png" /><figcaption>Chat-based VS Conventional UI</figcaption></figure><h3>Chatbots perform actions</h3><p>The theoretical benefit of chat-based UI compared to conventional UI is the freedom it gives. One might think:</p><blockquote>“Chat is a free form of communication and you can just type anything, so you are not limited to input forms and buttons like in conventional UI.”</blockquote><p>But in reality…</p><blockquote>A chatbot is a <strong>regular</strong> computer program that has <strong>limited </strong>functionality (at least now) with an unusual user interface.</blockquote><p><strong>About the limit: </strong>we can have chatbots that <strong>know</strong> everything (for example <a href="https://github.com/facebookresearch/DrQA">this project</a>) but we are far away from chatbots that can<strong> do</strong> more than few things. That’s why Apple’s Siri get new features/functionality only occasionally with iOS updates. The process of implementing new functionality in any bot (actually in any application) is <strong>not scalable</strong>. There will only be a finite number of cases your application handles. Scaling this will be the biggest advancement in chatbot history. In future posts I will share my personal vision of how this can potentially be solved.</p><p>What about Facebook M? In <a href="https://blog.arik.io/facebook-m-the-anti-turing-test-74c5af19987c">this article</a> a guy performs a so called anti-turing test to prove that M is not 100% AI.</p><p>So what’s the point of confusing users by allowing them to ask just about anything, while being able to perform only certain things?</p><p>A hypothetical chatbot for restaurant table reservations will have functionality like this: find a restaurant, reserve a table and manage previous reservation. And still conventional UI makes more sense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2L-ZgXQMnl648oHVxzQlw.png" /></figure><h4>Still don’t believe me?</h4><p>Let’s look at the evolution of the <a href="https://developers.facebook.com/products/messenger/">Messenger Platform</a> (a set of tools and APIs for developing chatbots for Facebook Messenger) and <a href="http://wit.ai/">wit.ai</a> (text classification and entity extraction service acquired by Facebook a couple years ago). At the beginning of Messenger, the emphasis was on text and very few rich content elements like buttons and templates with images. Buttons in text are indeed very useful, but if you think about it you will notice how strange it sounds. Imagine talking with somebody and during the conversation you notice buttons on their cheek, and if you select one, they’ll perform that action :)</p><p>What about web extensions? Oooh man, it seems like we are inventing the web and everyone is so amazed that we can finally have a web page in the chat, wow, what a miracle. What could be worse? A chat without the ability to send a text! Yes, you heard me right — in Facebook Messenger you can setup a chatbot that doesn’t support text messages!</p><p>The guys at <a href="http://wit.ai/">wit.ai</a> (read Facebook) are rockstars I’m sure; in the beginning, they created a cool way to design conversations that they called “stories”. But they recently <a href="https://wit.ai/blog/2017/07/27/sunsetting-stories">shut it down</a>, tossing a couple of years of work out the window. Why? Because they realized that people want buttons, web pages, and quick replies. Now wit.ai is just another user’s intent analysis and entity extraction tool, yet it’s one of the best and free of charge. Was this a wrong decision? No, it was inevitable.</p><p><em>Disclaimer: Facebook Messenger is the most popular and the most robust messenger with chatbot support and that’s why it’s used in my examples. I don’t have anything against it, actually, it’s my personal favorite and the platform of choice when we develop a chatbot.</em></p><h3>Is there ANY reason for chatbots to exist?</h3><p>We humans are all very intellectual beings, but in many cases our brain can’t distinguish what’s real and what’s not. We all know that movies are fiction, characters are not real people, and that cartoons are just pictures in motion, but it doesn’t stop us from connecting with them emotionally and sharing their feelings. And don’t forget computer games. Remember Tamagotchis? Just think about the obsession the human race had with those.</p><p><strong>Emotional connection</strong> is what’s missing from the conventional user interface of pages, forms and buttons. And that’s the most important ingredient we miss in chatbots. After analyzing more than a thousand user-to-bot conversations, we clearly noted that users expect something more from the chatbots then they would in the case of conventional UI. A simple example would be that users greet the bot, say thanks, ask how he(it?) is doing, and say goodbye. Can you imagine the same behavior on the web page or mobile apps? It would certainly be fun to watch :)</p><p>That’s why chatbots should have a personality and a distinct character. And that’s the reason why I hate any chatbot that offers something like this:</p><p><em>This is a Restaurant Bot, my commands are:<br>a - book a table<br>b - find a restaurant<br>c - go to hell</em></p><p>Emotional connection deepens the relationship with the user. Chatbots are becoming our best friends, humble, ready to help without hesitation and awake 24/7. They bring something very special to a human-computer interaction, an emotional bond, which results in more joy, more satisfaction and more engagement. This is the key element of chatbots we should not miss.</p><h3>Creating emotional connection</h3><p>The main challenge of creating a good chatbot is to develop a character. You should approach it not like you are developing a program, but a friend — though a virtual one. While this is a more complex and creative task, a few tips might help you ensure your chatbot is not too robotic.</p><ol><li><strong>Small talk </strong>—<strong> </strong>this<strong> </strong>is very important for any chatbot. For a chatbot to have a personality, it should be able to talk about common things and have some kind of opinion.</li><li><strong>Subtle sense of humor </strong>—<strong> </strong>giving your user’s little moments of happiness is what makes a chatbot great. When developing a chatbot, try to make it a bit playful and funny.</li><li><strong>Don’t pretend to be a human</strong> — from the first interaction, a chatbot should let the user know that it’s not a human in order to set users’ expectations. If a user believes they’re interacting with a human, at some point they might get angry and not understand why the hell the person on the other side doesn’t understand some basic things, which could make their experience disastrous.</li><li><strong>Be prepared for anything </strong>— the freedom of chat has its down side, which is that users might ask off topic questions or make general statements your bot is not designed to understand. Your bot should be honest about it’s capabilities and reply to off topic questions with something like “Hmm, I don’t know, I’m just a bot”, “Let me ask my creators”, “Good question”, or “That’s a good point”. This also helps give the bot a fun personality.</li></ol><p>You can find a more comprehensive list of tips in the article about <a href="https://medium.com/research-engineering-at-simply-technologies/10-conversational-ux-tips-every-chatbot-should-follow-491c2ccba220">10 Conversation UX Tips Every Chatbot Should Follow</a> by Loric Avanessian, a senior UX consultant at IBM, and myself.</p><blockquote>Emotional connection is the essential element every chatbot needs to provide</blockquote><h3>Conclusion</h3><p>Don’t get me wrong, I’m a passionate advocate of chatbots and conversational UI, and we’re now in the first stage of the technology adoption lifecycle, a kind of stone age of the chatbots epoch, which means there are more experiments than real useful cases. In order for chatbots to become something more than just cool fad, a lot of technology advancements and experiments need to be done. Still, they are already used by many people. Nevertheless, chatbots finally bring something very new and special to the human-computer interaction, and that is an emotional connection.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=521d67eb0b61" width="1" height="1" alt=""><hr><p><a href="https://medium.com/research-engineering-at-simply-technologies/why-i-hate-chatbots-yet-still-love-them-521d67eb0b61">Why I hate chatbots… yet still love them</a> was originally published in <a href="https://medium.com/research-engineering-at-simply-technologies">Research &amp; Engineering at Simply Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Conversational UX Tips Every Chatbot Should Follow]]></title>
            <link>https://medium.com/research-engineering-at-simply-technologies/10-conversational-ux-tips-every-chatbot-should-follow-491c2ccba220?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/491c2ccba220</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Mon, 04 Sep 2017 12:38:06 GMT</pubDate>
            <atom:updated>2017-09-06T07:45:18.585Z</atom:updated>
            <content:encoded><![CDATA[<p>The hardest part of designing a chatbot is undoubtedly the conversation. The interface is relatively simple, particularly if you’re building a bot for an existing platform like Facebook Messenger or Slack, but that just means that the conversation content is going to be in even greater focus.</p><p>Just like when designing any digital product, the role of UX is to advocate for the user. What is the user’s goal? Why are they using your bot? What do they expect to get out of it? How long do they expect it to take? How do you want them to feel while interacting with your bot? All of these are questions to keep in mind when beginning the design process.</p><p>Conversations with a chatbot should always feel fluent and organic — speaking with others is a natural part of human interaction, which means it’s incredibly difficult to simulate. In conversation, we naturally jump from topic to topic, ask for clarification, and use words and phrases that convey our emotions. Below are a few tenets of chatbot conversation design that can help shape the experience your users have with your bot.</p><h3><strong>1. Don’t pretend to be human</strong></h3><p>You should always make it clear to your users that they are chatting with a bot, and not an actual human. This sets expectations for the user, and allows you to build a unique personality for your bot. There are differing thoughts on whether a bot should use the typing indicator before sending messages — some people believe it gives the appearance of a human typing which is misleading, while others think it makes the conversations feel more natural. If you fail to set expectations with your users, they could misunderstand the limits of the functionality, leading to frustration and a less than satisfactory experience.</p><h3><strong>2. Provide an introduction</strong></h3><p>Using a chatbot isn’t intuitive for most people — yet. Provide an introduction to your bot, and explain what it can do for your user, and how they should interact with it. Lay out your bot’s value proposition front and center.</p><h3><strong>3. Help guide the conversation with smart hints</strong></h3><p>Helping users navigate conversation with your bot can be extremely beneficial for two reasons. First, by suggesting inputs, you can guarantee that your bot will know how to respond, and therefore your user won’t “break” the conversation loop. Second, it takes some of the pressure off of your user, who may not know what they can ask or how they can interact with your bot. As bot technology becomes more sophisticated and widespread, the need for these smart hints may diminish.</p><h3><strong>4. Keep pace with your user</strong></h3><p>If the bot needs to send large amounts of text, do so gradually as separate text bubbles. Allow for some time in between each text to allow your user to read the information. It’s easier for your user to digest the text this way, rather than as a single block.</p><h3><strong>5. Give your bot personality</strong></h3><p>Just because your user isn’t interacting with a human doesn’t mean your bot should sound stiff. Give your bot a personality that reflects your brand’s identity and voice. Use friendly, simple language to interact with your users. One of the main differentiators between chatbots and traditional UI is the potential for establishing an emotional connection with your users. Giving your bot personality is the easiest and most natural way to do this.</p><h3><strong>6. Keep track of the conversation</strong></h3><p>Simple things like remembering the last time your bot interacted with the user can help make the conversation feel more natural. For example, you don’t need to greet a user who’s last interaction was 10 minutes ago.</p><h3><strong>7. Avoid open ended questions</strong></h3><p>Because you’re going to have to validate all of the user input that comes through your chatbot, avoid open ended questions that could be potentially tricky to respond to. This is where hints can also help guide conversation.</p><h3><strong>8. Use rich UI elements where appropriate</strong></h3><p>One of the advantages to building bots for existing platforms like Facebook Messenger is that they offer rich UI elements to help make interacting with your bot easier. Using photos, action buttons and links can help make the interactions more rewarding.</p><h3><strong>9. Confirm input</strong></h3><p>Just like when designing other interfaces, data must be validated, except this time, it’s done through conversation. When you ask the user for information, such as their address, always confirm the information before acting upon it. If your bot asks for a phone number and the user answers with letters, gently explain what kind of information you need.</p><h3><strong>10. Small talk is important</strong></h3><p>It’s important to have at least basic support for small talk like greetings, goodbyes, and saying thank you. It’s even better if your bot understands the time of the day and responds accordingly. Remember, even if your users have a clear understanding that they are talking to a bot, they should still have some emotional connection with it, and that’s the biggest difference between chatbots and other human-computer interfaces.</p><p>As chatbots become more widespread, more and more best practices will surface. The best way, as always, is to build and test continuously with users. Particularly when it comes to designing natural conversation, your best resources are the people who surround you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=491c2ccba220" width="1" height="1" alt=""><hr><p><a href="https://medium.com/research-engineering-at-simply-technologies/10-conversational-ux-tips-every-chatbot-should-follow-491c2ccba220">10 Conversational UX Tips Every Chatbot Should Follow</a> was originally published in <a href="https://medium.com/research-engineering-at-simply-technologies">Research &amp; Engineering at Simply Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Facts About Chatbots That Will Impress Your Business Partner]]></title>
            <link>https://medium.com/research-engineering-at-simply-technologies/8-facts-about-chatbots-that-will-impress-your-business-partner-4ee1de804a7e?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ee1de804a7e</guid>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Thu, 31 Aug 2017 09:29:41 GMT</pubDate>
            <atom:updated>2017-09-04T12:32:50.167Z</atom:updated>
            <content:encoded><![CDATA[<p>Today chatbots are not something futuristic, they already became something very usual for a big number of people. Each day new businesses start using chatbots. So what are the main reasons businesses all over the world invest resources in this new paradigm? Here is our own compilation of facts we believe drive the adoption of chatbots.</p><h4>#1 There are 1.2B Monthly Active Users on Facebook Messenger</h4><p>An astonishing number of users in the Messenger makes it the biggest messaging platform on the earth. The potential reach of one’s chatbot is 1.2 billion users. That’s why it is so attractive platform for chatbot developers.</p><h4>#2 90% of Social Customer Care Happens on Facebook</h4><p>According to the research by Socialbankers, 90% of all social customer care happens on Facebook and most of it are private messages. 56% of companies say social customer care has a positive return on investment.</p><h4>#3 There are More than 34k Messenger Platform Developers</h4><p>The Messenger ecosystem is thriving, in one year it was able to create a big community of developers for this particular platform. 34k developers created more than 30k chatbots.</p><h4>#4 Nearly 60% of Millennials Have Already Used Chatbots</h4><p>According to the survey conducted by Retale, nearly 60% of millennials have already tried chatbots. And about 70% of them liked the experience.</p><h4>#5 On average, companies take 600 minutes to respond to a private message</h4><p>As crazy as it sounds in average, it takes 10 hours to respond to the private message. While Canadian telecommunication company Rogers have seen <strong>65% increase in customer satisfaction, </strong>by automating private messaging, that’s an incredible result showing us what we can potentially reach.</p><h4>#6 The Global Trend — Private messaging increased while wall posts decreased</h4><p>Research shows that people all over the world started using more private messaging and less public commenting when they communicate with businesses.</p><blockquote>Most social media communications are now private, enclosed inside one-on-one direct-message conversations. That suggests the market opportunity for AI bots is equivalent to a majority of the current market for social media customer care.</blockquote><blockquote>Business Insider</blockquote><h4>#7 Chatbots can be Multi-language</h4><p>Chatbots are not limited to English as you might think. Businesses can have a chatbot that understands many languages and talks many languages making it easier expanding your potential reach. With the recent update to the Messenger Platform Facebook added a feature which allows having the persistent menu in different languages.</p><h4>#8 24x7 Customer Support Made Easy with Chatbots</h4><p>Have you ever dreamed of having a customer support team working 24x7? With chatbots it’s easy, they are basically computer programs working forever &amp; non-stop.</p><p><strong>Takeaway</strong>: No matter in what field is your business, you should already consider using chatbots. They have a potential of increasing sales, improving customer satisfaction, promoting your business and saving you time and money.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ee1de804a7e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/research-engineering-at-simply-technologies/8-facts-about-chatbots-that-will-impress-your-business-partner-4ee1de804a7e">8 Facts About Chatbots That Will Impress Your Business Partner</a> was originally published in <a href="https://medium.com/research-engineering-at-simply-technologies">Research &amp; Engineering at Simply Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Every Software Engineering Team Should Learn From Football Teams About Team Building And Use…]]></title>
            <link>https://medium.com/@alexadamyan/what-every-software-engineering-team-should-learn-from-football-teams-about-team-building-and-use-7f99dd80f669?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f99dd80f669</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Sun, 02 Aug 2015 12:23:17 GMT</pubDate>
            <atom:updated>2015-08-02T12:23:17.162Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Every Software Engineering Team Should Learn From Football Teams About Team Building And Use It Right Now</h3><p>No matter what industry you are whenever there is a team behind a product or service having a real teamwork with fueled with great spirit is among the most important factors for success. It’s clear that team capacity is much more than sum of it’s members as individuals, simple math isn’t working there.</p><p>It’s easy to say how important it is, but very very tough to build a team, to train your individuals to think “team”, particularly I’m talking about software engineering teams. On the other hand it’s not a new topic at all, teams were there for tens of thousands years, starting probably with humans hunting animals that otherwise would not be possible or very dangerous for individuals to hunt and later appearing in every game where group of people compete with opponent group or for some goal. Probably the most popular team game around the globe is a football(soccer), pure team game where it’s impossible for any team to win without teamwork.</p><blockquote>“Talent wins games, but teamwork and intelligence win championships.” — <em>Michael Jordan</em></blockquote><p>While most of the football teams are good spirited teams, most of the software engineering teams are just bunch of individuals. Let’s compare similar situations between software engineering teams and football teams at first just for fun.</p><h4>Situation #1</h4><p>Your teammate has finished all assigned tasks, did all commits, merged the code with others, logs every minute spent in the timesheets, updates the task tickets, stands up and say goodbye to everyone and goes home. Sounds like a good employee. Meanwhile in football imagine a player kicks a goal, stadium applauded and whistled, he even became the best player of the season, shake hands with teammates, say goodbye and proudly leaves the stadium thinking <em>“what a good player I am… I’ve done my job, it’s time to go have some fun, you guys stay there with your problems, I don’t care”. </em>Very funny.</p><h4>Situation #2</h4><p>Your teammate has hard time figuring out the issue with some hardcore technology, struggling with some bad documented library, trying to deploy the release while there is some unknown error on the server-side with no output and no debugging possible or thousand of other situations happening many times with all software developers and it takes an indefinite time to finish that task. While others in the team having their “own” problems, busy with their current tasks or just ignoring team mate’s struggling, no one is helping, they just leave him alone. Seems reasonable again. In the football — a player has a hard time, pushed by opponent team with 5 againts 1, every one from his team looking and do nothing, one got a popcorn from somewhere watching, another got his smartphone chatting with girlfriend on Facebook, the wisest ones exercising but no one moving towards the teammate to support him.</p><h4>Situation #3</h4><p>Your teammate is sick or has some personal issues, tasks assigned to him being collected day after day to a big pile. Others are busy with their current assignments, nobody cares since they have their own problems, no one takes the responsibility. Sounds like that’s the way it should be. In the football imagine a player got a red card and shall be removed from the field leaving a team with 10 players of 11 and the team hasn’t change their positioning layout. There is a gap in the field, a place where the player was intended to be is empty, the opponent team has no trouble using that empty part to kick goals again and again. Everyone seems to do their job and playing full force, but nonetheless they lose.</p><h4>Situation #4</h4><p>Your teammate learned something very cool or got some experience using a particular technology, mastered some library or framework, he is very proud of him being so smart. Using that experience he is able to close task after a task with higher quality and drastically less effort. Looks like you have a genius in your team, congrats! Meanwhile in the football imagine a player who is more skilled always keeps the ball, never perform a pass to others, thinking <em>“hey I’m not going to give you the ball, you just can’t play with it like I do” </em>always tries to run the field from the one end to another to kick the goal, but that’s just one guy versus a 11 opponents.</p><h3>Tips &amp; Tricks</h3><p>Because of this particular issue of not having a good team billions of dollars wasted each year. The bad team is bad efficiency.</p><blockquote>“None of us is as smart as all of us.” <em>— Ken Blanchard</em></blockquote><p>The team building is an endless process and it’s not possible for me to cover all topics even if I could know all of them, but based on my personal experience I would like to share some tips that will probably make your team spirit healthier whether you are a team member or a manager.</p><h4>Tip #1</h4><p>Whenever you have finished your tasks don’t rush to turn your computer and run away from the office. A good step towards to a great team will be to ask your team members whether they need your help. Be 100% honest to help your team, without asking anything in return, do a generosity step. We all love when we feel that there is someone ready to help and we will do the same during the next opportunity. Be the first to start caring about your teammates and be sure they will do the same in return.</p><h4>Tip #2</h4><p>When you see your teammate has hard times, struggling, offer your help. Most probably you have your ongoing tasks to finish, but that doesn’t really matter as the project you are working on has to be finished in every part of it. Support your colleagues and then get back to your ongoing tasks. Be sure by doing this you will get much more support from your teammates next time you will be struggling. Be the first to help!</p><h4>Tip #3</h4><p>When a teammate’s absent, the rest of the team should take care of the extra work to make sure that when their colleague be back he/she will not face an infinite pile of tasks that he will never be able to finish with quality and catch up with the rest. Once you have offered your help be sure on the day when you will need a day off the whole team will be there for you!</p><h4>Tip #4</h4><p>Whenever you learn something cool that makes everyone’s job easier share your knowledge immediately , make your co-worker’s skills rising, teach them every single thing you know they might need, work to make your team smarter, stronger and wiser. Sharing is giving and by giving you will get much much more.</p><p><em>Football players not just support each other… they literally love each other.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D8P3m4zOIfBpAvssLtJEdw.jpeg" /><figcaption><em>credits to Athena Picture Agency (www.athena-pictures.com)</em></figcaption></figure><h4>Conclusion</h4><p>Stick to each other like you have been glued with superglue. Be one for all and all for one and remember only being together you will be able to do things much more bigger and valuable than you are and to be proud by your achievement the rest of your life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f99dd80f669" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Absolutely Mandatory Questions You Should Ask During The Interview]]></title>
            <link>https://medium.com/@alexadamyan/5-absolutely-mandatory-questions-you-should-ask-during-the-interview-feec65d0b498?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/feec65d0b498</guid>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Fri, 31 Oct 2014 09:59:18 GMT</pubDate>
            <atom:updated>2014-10-31T09:59:18.004Z</atom:updated>
            <content:encoded><![CDATA[<h4>Personal experience on hiring by software development company founder</h4><p>I&#39;ve founded my second company early in 2011, Simply Technologies, a software development company. Being a software developer myself the most important mission was to create a company where I would absolutely dream to work. I had a lot of experience by that time, almost 9 years working in different companies, big and small, I learned a lot during that period and had a clear picture on how my company should be different. To be honest, I always had a dream to establish own company.</p><p>So in February of 2011, my friend and me quit our jobs towards our dreams. It was a start of the most interesting three and half years in my career, I would say most productive years, since my responsibilities expanded from just software developer to something more, much more. As you can imagine having a start-up company brings a lot of diverse tasks on founders, more over we still had our full time commitment in the software projects as developers. So these include from administration, accountancy, customer facing/sales, technical leadership, team leadership, and many many other things you could never predict would be a part of your job. But the most important task and one of the most interesting was the hiring process.</p><p>So today I will talk about the process of hiring we were using that helped us to grow from 2 founders to 16 persons dream team, the team of great minds we are so proud of. In my opinion the most important part of the interview is to understand whether the guy you are interviewing has the right mindset required for the position. This is a continuation to my first post about inspiration, and now I will tell you about my approaches on how to understand whether the person is “inspirable” or not. Of course I did mistakes, but I learned from them and now sharing my experience which hopefully will save some valuable time for somebody while building a great team.</p><p>I believe that following questions will give you almost 99% results if you listen to the answers carefully.</p><p>Lets start!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nremt9HEVM7iF2GSkuiIaw.jpeg" /></figure><h3>Do you love your profession?</h3><p>This should be obvious, but it really happens, actually it happens a lot that the person you are interviewing doesn&#39;t really like what he’s doing. Especially it happens more often in software development business and the reason probably is that the salaries are comparably higher and it is always on demand in any part of the world.</p><p>I believe that every single person could be successful, the most important thing is to choose the right profession, the one that is joyful and gives you personal satisfaction, the one that you love. There is no a software developer that is great but doesn&#39;t really love his profession, it’s absolutely impossible! And almost always the ones who really love what they are doing have great acknowledgment and success. So if you are looking for great minds this rule is mandatory.</p><p>To understand that just ask a direct question “do you love your profession and why?” and watch carefully. You should see that there is a true love by passion of telling, fire in the eyes and ideally you should be inspired by the story about the “why do you love it”.</p><p>If there is no a positive sign of love, just stop the interview, it’s just a waste of your and interviewee time, that’s why this is the first question in my list. Additionally in such cases I’m trying to ask different questions just to help the person to find that something he is passionate about. There is always something for anybody.</p><h3>What are the three most important things about your work?</h3><p>This question will help you to understand whether there is a strong connection between your value sets, things like whether it is important to have beautiful code along with beautiful and usable interface of the application, or how important is the quality of the product you are building, the importance of sharing knowledge with others, the importance of the helping out team members in the time of need, the importance of the project you are working on, the technologies used, the approaches of development, the processes and just many other things you will hear by asking this question will give you more information about the values of your potential employee than any other way. Understanding the connection of value sets and having a strong one is crucial for building a great team, the team of harmony and great collaboration.</p><p>I&#39;m always asking about the three most important things but never limit the conversation if there is something more to learn, just this way it is easier to trigger the interviewee to think about the important things in priorities.</p><p>And again if there is a huge gap between the values, stop the interview, otherwise you probably gonna end up with infinitely long debates about every single thing ☺</p><h3>What inspires you?</h3><p>My favorite one. First ask this question to yourself. Remember the time when you were inspired about the work you were doing, creating something, learning about something exciting… try to feel it again, get that genuine feeling and think in details. Now when you are ready speak about your inspiration and see if there is a response from interviewee. Does he get inspired? If yes, try to understand what particularly inspired him. This technique helps you to open up the inner places of the person where he is getting inspiration. Ask what else he is inspired about and get inspired by yourself.</p><p>As you can imagine this is the most inspiring part of the interview ☺</p><p>If you were not able to inspire him, but you are 100% sure you were inspired when you were talking, probably it is not the right person for your team as the chances that you will be able to inspire him later on are very very small.</p><h3>What motivates you?</h3><p>While inspiration is more spontaneous and spiritual kind of thing and happens regardless of any schedule and plans, motivation is something different, it should be well thought through and you should have some ideas on how to motivate and create a motivational environment for your team. And as you probably know there are two kind of motivation intrinsic and extrinsic. While extrinsic motivators are based on rewards and so applied externally, intrinsic motivators are self generated inside a person and associated with satisfaction, acknowledgement, bigger purpose and moral values and so are more powerful and natural. Actually after watching Dan Pink’s TED talk <a href="http://go.ted.com/FLq">“The puzzle of motivation”</a> (one of my favorite) I completely declined external motivators and now recalling the years of working in other companies I can clearly state that I was never motivated by bonuses and money. Of course those things matter, but what I&#39;ve realized is that things like money never can help you to increase the performance in types of work that involve cognitive thinking and creativity, so particularly in software development. In past years I have many debates about this topic but I’m really convinced about it mostly because I fell it myself. In fact as you can see in the TED video extrinsic motivators may even harm the productivity, that’s really not something we see around us and for the most people it seems ridiculous. What you really need to achieve is to make sure your team members feel secure and safe. They should absolutely continuously feel the care about them like you care about your close friends and family in a very natural way, no fakes!</p><p>So coming back to the interview question, here your job is to understand that things like great team, interesting and challenging projects, new technologies, satisfaction on successful project delivery, nice office environment, daily freedom, knowledge sharing, hackathons and geeky things are among the top motivators of the person you are interviewing. Unfortunately some people who had worked in the environments where the main motivators were bonuses, later-on had difficulties switching to the intrinsic motivators model and probably will not be able to integrate with your existing team, even it could affect others in the bad way. So basically if there is money on the first place you got the wrong guy and its time to stop the interview ☺</p><h3>Do you invest in self-improvement and how?</h3><p>In many professions and especially in the software development learning and self-improvement is crucial due to very frequent technological changes, new languages, new frameworks, new libraries and platforms released every day. So learning must not be optional but one of the most important part of work everyday. Believe me or not, but if your team members don&#39;t spend time on learning or don&#39;t have time in one, two years you will end up with a team of cavemen.</p><p>Just ask this question and listen carefully how the person do self-improvement, and practically ask what did he learn in past month, week, yesterday, what was the reason for that, does he have an initiative on learning new things or only do so because some need.</p><p>Most probably if you have a guy passed through the first four points here he should also demonstrate great learning skills, but there are always exceptions.</p><p>If you got here I’m absolutely sure that you have found a person that is very enthusiastic and passionate, loves his job, has same values as you and probably the rest of the team and invest significant time in learning.</p><blockquote>Will be happy to learn about your experience in hiring or being hired ☺</blockquote><blockquote>Hope you find this post useful</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feec65d0b498" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inspiring your team: no science — just personal experience]]></title>
            <link>https://medium.com/@alexadamyan/inspiring-your-team-no-science-just-personal-experience-f26db1a9e879?source=rss-50d2751ed15b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f26db1a9e879</guid>
            <dc:creator><![CDATA[Alexander Adamyan]]></dc:creator>
            <pubDate>Fri, 24 Oct 2014 14:53:07 GMT</pubDate>
            <atom:updated>2014-10-24T15:11:42.243Z</atom:updated>
            <content:encoded><![CDATA[<h2>Inspiring Your Team</h2><h3>No Science, Just Personal Experience</h3><p>Recently I found an article about the difference of motivation and inspiration, really great one, not surprisingly an inspiring one☺Here’s the link <a href="http://paidtoexist.com/inspiration-vs-motivation/">inspiration vs motivation</a>.</p><p>So what is inspiration for me. The simplest answer: it is when you fell in love with something… or… you share your love with someone who fell in love with that something. And this is why: just remember when you was inspired last time. It’s all about feelings, emotions, joy and happiness, it’s when you are sure you are in the very right mood and at that very moment the only thing matters is something you are inspired about. It’s when you feel an incredible driving force from your inside. Inspiration is so deep inside us that we are not able to describe it in more structured way, it’s in our <strong>subconscious </strong>and it’s out of our control. This is the definition of love for me.</p><p>But how to make others to love something, even though it is not something possible by definition. How to inspire someone? In the first place and the most importantly you need to be inspired yourself, inspired very deep, like a little baby interacting with yet undiscovered world, world of surprises, colors, lights, sounds, spectacular things and finally beautiful life. If you don&#39;t have that genuine feeling you will never be able to inspire, though you can still try to motivate, but that’s another story.</p><p>OK, suppose you have an inspiration, so how should we transfer it to someone? First we all should remember that inspiration is not something you can impose on anybody. The only way like I said is to share it and if you do it with all passion you have, probably someone will fall in love and so get inspired too. You should show all the inner beauty of the world where you get inspiration, share your all deep feelings about it, without getting shy, with a strong confidence about your emotions, so pure and clean, share the fire in your eyes, show the happiness, joy and your values.</p><p>I’m sure that nobody will ever able to resist.</p><h3>Every day</h3><p>Part of my every day’s job as the owner of the software development company is to inspire teams. Actually my favorite part. But it is not something you do with some predefined schedule, rules, plans… you know what I mean. It should be so natural that whenever you talk to your employees, every moment of communication should contain the inspiration you are living with. Remember, it is a feeling and you should feel in your bones.</p><h3>“Uninspirables”</h3><p>Sometimes it could happen that someone from the team doesn&#39;t get inspired while others do. Probably it is because of inspirer is not doing his job well, but maybe it is because that the guy is not sharing the same values set as you. Unfortunately I didn&#39;t came up with a solution so far for this issue (would be happy to hear about your experience/thoughts), so I believe the most important part of the interviewing candidates is to try to inspire them and if there is a connection most probably you found the right person for you team. Next time I will share my ideas how to test candidates whether they are “inspirable” or not. The precondition is that you already able to inspire at least the vast majority of your staff.</p><blockquote>true only if you found it inspiring</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f26db1a9e879" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>