<?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 Alexandra Efrimov on Medium]]></title>
        <description><![CDATA[Stories by Alexandra Efrimov on Medium]]></description>
        <link>https://medium.com/@alexandraefrimov?source=rss-a13cc1ebad0c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ydZS1g0itcygF1HtUrYxWw.jpeg</url>
            <title>Stories by Alexandra Efrimov on Medium</title>
            <link>https://medium.com/@alexandraefrimov?source=rss-a13cc1ebad0c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:20:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexandraefrimov/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[Product discovery phase: Make it or break it in 3 steps]]></title>
            <link>https://uxdesign.cc/product-discovery-phase-make-it-or-break-it-in-3-steps-812ba9a654a?source=rss-a13cc1ebad0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/812ba9a654a</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[Alexandra Efrimov]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 11:06:17 GMT</pubDate>
            <atom:updated>2023-05-25T09:24:54.090Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Banner illustration with light bulbs on a yellow background" src="https://cdn-images-1.medium.com/max/1024/1*pfS8dGBRVlWN30PMM38ZKA.jpeg" /></figure><p>It is estimated that 9 out of 10 startups fail. Yes, the numbers are staggering and the odds seem to be against us, but winning the battle could be as easy as figuring out what doesn’t work and doubling down on what does.</p><p>In 2019 CB Insights conducted a <a href="https://www.cbinsights.com/research/startup-failure-reasons-top/">survey</a> to answer the question on everyone’s minds: <strong>“Why do startups fail?”</strong>. Surprisingly, while this is rarely a single-culprit issue, the most common reason is a lack of market demand. Simply put, most startup failures happen because their product or service does not respond to the needs of the customer.</p><p>Other <a href="https://s3.amazonaws.com/cbi-research-portal-uploads/2018/02/02135131/00-chart-3.png">common reasons</a> why businesses fail in the early years include:</p><ul><li>Insufficient financial resources</li><li>Putting together the wrong team</li><li>Getting outcompeted by others in the market</li><li>Pricing and cost issues</li><li>Lack of a business model</li><li>Lack passion and innovation</li></ul><p>So how do we beat the odds and make sure our product meets the needs of the market?</p><p>This is where the <strong>Discovery Phase</strong> comes into place — the the most overlooked and underestimated phase of the product development lifecycle.</p><p><strong>What is the Discovery Phase?</strong></p><figure><img alt="A graph showing the evolution of uncertainty throughout the different phases of the software development process" src="https://cdn-images-1.medium.com/max/800/0*0ngcjt7aaYkHtDKX.png" /></figure><p>The Discovery Phase is the first stage of the software development process. Also known as the research or the analysis phase, its main purpose is to help you gain a deeper understanding of the business needs and requirements.</p><p>It brings together stakeholders, product experts, designers and software architects, whose combined expertise can offer a holistic view of the opportunities and challenges involved.</p><p>At this point in the process, the main focus is to gather as much information as possible about the market, the target audience and the competition. What we want is to validate the business idea in order to determine if the project is worth investing your time and money in. More importantly, we want to ensure that the product is solving a real problem for real people. Keep in mind that, as mentioned earlier, the number one reason startups fail is because of lack of market need.</p><p>If done right, it will get your questions answered and from there on you can make calculated decisions whether to move forward with developing the project or not.</p><p>Here at <a href="https://mcro.tech/">MCRO</a> we advise all our customers not to jump into design and development without having a clear vision of what their product will entail. The Discovery Phase means having a dedicated team of experts validate your idea, kickstart your project and lay the foundation for success.</p><p>So let’s jump right into it and take a look at how it works and how it can benefit your business.</p><p><strong>How does it work?</strong></p><figure><img alt="Illustration displaying the 3 phases of the Discovery Phase: Understand, Ideate and Decide" src="https://cdn-images-1.medium.com/max/740/0*wgsM39VHW57ipGDX.png" /></figure><p>While every project has its own unique needs and rhythm, the Project Discovery Phase typically follows the structure listed below:</p><p><strong>1. Understand</strong></p><p>The understanding phase focuses on identifying the needs of the users and aligning them with the needs of the business.</p><ul><li>Who are the users?</li><li>What are the challenges you are trying to address through the product?</li><li>Who are your competitors and how can we gain advantage over them?</li></ul><p>Conducting extensive research, studying the competitors and identifying the personas are the first steps towards designing a solution rather than just a product.</p><p><strong>2. Ideate</strong></p><p>With the knowledge gained from the previous step we are able to start coming up with solutions, define requirements &amp; software architecture, start working on wireframes and even engage with the potential users to get early feedback.</p><p>At this point there is no good or bad, it’s a trial and error stage where you have the freedom to experiment. At the end of the day, you need to provide something new to the market and solve problems that others were not able to solve.</p><p>There’s a quote from <a href="https://www.danpink.com/about/">Daniel Pink</a> which guides our mindset when it comes to providing creative solutions to our customers:</p><blockquote>“Believe it or not, many people don’t care how awesome your product is. Instead, they care about how awesome they are when they use your product.”</blockquote><p><strong>3. Decide</strong></p><p>You now have all the data you need, all the necessary requirements, wireframes and research information to make a calculated decision. This is the moment you decide whether to invest into the next solution for your potential customers or rethink the whole project.</p><p>It’s easier to decide which way to go when all the risks are identified and you have a clear understanding of the market and the target audience.</p><p>Let’s say you find out your idea is not worth pursuing-you dodged a bullet and prevented losing hundreds of thousands of dollars down the line. Moreover, identifying what doesn’t work is only bringing you closer to what does.</p><p>On the other hand, if the outcome is a positive one and decide to go through with development, you now have the advantage of having laid the foundation for a successful product.</p><p><strong>What are the benefits of a Discovery Phase?</strong></p><p>If you’re not convinced whether or not Product Discovery is a good fit for your project, let’s have a closer look at some of the benefits of undertaking pre-development research and analysis with a dedicated product team:</p><ul><li>Clearly define <a href="https://www.pmi.org/learning/library/project-scope-statement-skills-tools-7981">the scope of the project</a> and the desired outcomes;</li><li>Develop a solid understanding of your target audience, their expectations and the market in general;</li><li>Validate your idea against market requirements and make sure that your product solves real problems for its potential users;</li><li>Identify possible risks and develop a response plan in advance;</li><li>Prevent costly changes during the development phase;</li><li>Find out whether or not the contractor—or the team, in general—is <a href="https://mcro.tech/find-the-right-app-development-company-to-build-your-app/">a good fit</a> before embarking on the development process.</li></ul><p><strong>Product Discovery Deliverables</strong></p><p>The final stage of the Discovery Phase is where everything comes together into a viable product concept; the most valuable outcome is a shared, highly documented understanding of the project scope and vision.</p><p>So what exactly will you end up with?</p><p>Every project is different in size and complexity, but here’s what the resulted product documentation typically includes:</p><ul><li><a href="https://www.atlassian.com/team-playbook/plays/customer-journey-mapping"><strong>Customer Journey Map</strong></a> — A visual representation of the process your customers will go through while using your product. Getting into the mindset of the user can be tricky, but it helps you identify their needs and develop effective solutions.</li><li><strong>Feature List</strong> — A list of key features based on business requirements and user expectations.</li><li><a href="https://www.usability.gov/what-and-why/information-architecture.html"><strong>Information Architecture</strong> </a>— A product blueprint designed to map out its infrastructure, features and hierarchy.</li><li><a href="https://www.usability.gov/how-to-and-tools/methods/wireframing.html"><strong>Wireframes</strong></a> — A low-fidelity representation of your digital product framework.</li><li><strong>Technology Stack</strong> — A tailor-made technology stack to meet your unique needs, one that delivers the most value for your money.</li><li><a href="https://www.nngroup.com/articles/ux-roadmaps/"><strong>Project Roadmap</strong></a> — An overview of your project’s goals and objectives presented on a timeline.</li><li><strong>Budget</strong> — A cost estimate and budget required to successfully deliver the project.</li></ul><p><strong>What’s next?</strong></p><p>At this point you should be ready to kick-off the implementation phase. Once your idea is validated and you have refined your solution to effectively respond to the needs of the user, you are ready to move forward with your project and build an MVP.</p><p>If you have a great product idea that you want to validate, or simply want to learn more about the Discovery Phase, <a href="https://mcro.tech/contact/">drop us a line</a> and our product team will be more than happy to help.</p><p><em>Written by </em><a href="https://medium.com/u/a13cc1ebad0c?source=post_page-----54d75d47e860----------------------"><em>Alexandra Efrimov</em></a><em> and Vlad Zahan. Originally published at </em><a href="https://mcro.tech/product-discovery-phase/"><em>https://mcro.tech</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=812ba9a654a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/product-discovery-phase-make-it-or-break-it-in-3-steps-812ba9a654a">Product discovery phase: Make it or break it in 3 steps</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[Adopting a remote-first company culture in the time of Coronavirus]]></title>
            <link>https://medium.com/mcro/adopting-a-remote-first-company-culture-in-the-time-of-coronavirus-54d75d47e860?source=rss-a13cc1ebad0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/54d75d47e860</guid>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Alexandra Efrimov]]></dc:creator>
            <pubDate>Mon, 23 Mar 2020 12:07:52 GMT</pubDate>
            <atom:updated>2020-03-23T12:12:09.249Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DIhjtyCDXUuOpLaXh24Ymw@2x.png" /></figure><p>Coronavirus cases continue to rise globally, with over 200,000 confirmed cases and 8,000 deaths as of March 18. In a relatively short amount of time, the outbreak has spread to over 150 countries and territories across the world. The threat is real and people are becoming increasingly concerned as more cases with no clear epidemiological links are discovered every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*S1xh026FZC55sFv_zRbmLQ@2x.png" /><figcaption>COVID-19 Outbreak World Map per Capita</figcaption></figure><p>The best we can do at this point is to adopt everyday protective behaviours, as recommended by the <a href="https://www.who.int/emergencies/diseases/novel-coronavirus-2019/advice-for-public">World Health Organization</a>.</p><p>As a preventive measure, an increasing number of companies are restricting business travel and encouraging their employees to work from home. Major companies such as Apple, Microsoft, Google, Facebook, Linkedin and Twitter have joined the remote movement in response to Covid-19 concerns.</p><p>As more and more companies take measures to protect their employees, it is now more important than ever to consider transitioning your team to remote work, even if it’s just a temporary measure.</p><p>Studies show that working from home has a number of benefits, including increased productivity and decreased employee turnover. But we need to keep in mind that such studies monitored employees over the course of months, if not years, and in different circumstances.</p><p>In the case of Coronavirus-driven remote work, it’s a whole different story. For one, we might be talking about longer periods of isolation. Loneliness and lack of social interaction is a problem in itself. Moreover, companies might be forced to make the transition to remote work overnight. Becoming a remote-first company is not an easy undertaking and it requires planning and preparation time. Putting together a remote work policy in such a short amount of time is a challenging task, but it’s not impossible.</p><p>Here’s what you need to keep in mind when transitioning your team to remote work:</p><p><strong>1. Communication</strong></p><p>First and foremost, communication is the most important aspect of working remotely. Teams need to be able to collaborate efficiently. Besides email, there are numerous tools and platforms for real-time messaging and videoconferencing that can help your employees stay connected.</p><p>Tools such as <a href="https://slack.com/intl/en-ro/?eu_nc=1">Slack</a>, <a href="https://zoom.us/">Zoom</a>, <a href="https://www.skype.com/en/">Skype</a> and <a href="https://hangouts.google.com/webchat/start">Google Hangouts</a> are all great choices, but regardless of what your team decides to use, it is important to set expectations and outline a communication strategy framework.</p><ul><li><strong>Settle on fixed meeting times</strong> and make it clear that everyone is required to join. Setting up a shared calendar and creating recurring events will ensure that everyone on your team is on the same page.</li><li><strong>Take into account time zones.</strong> Scheduling meetings across multiple time zones can be quite challenging. If you find yourself in a logistical pickle, keep in mind that nowadays there is a solution (or an app) for everything. Tools such as <a href="https://www.timeanddate.com/worldclock/meeting.html">Timeanddate</a>, <a href="https://www.agreeadate.com/time_zone_planner.aspx">Agreeadate</a> and <a href="https://everytimezone.com/">Everytimezone</a> can help you find the best time for your meetings.</li><li><strong>Establish an effective meeting cadence.</strong> How often you should meet is up to you and your team. Setting up the right meeting cadence is not something that happens overnight. Try experimenting with different patterns (e.g., daily standups, weekly meetings, all-hands); the goal is to find the one that maximizes productivity for your team.</li><li><strong>Encourage video conferencing.</strong> Face-to-face interaction can ensure that we don’t lose emotional context. Non-verbal cues provide important context, allowing information to be conveyed effectively, even across language and culture barriers.</li></ul><p><strong>2. Project Management</strong></p><p>Becoming a remote-first company requires rethinking your project management processes and aligning them with the new circumstances. Keeping track of everything when working with distributed teams might turn out to be a bit more challenging at first, especially if this is a whole new territory for your company.</p><p>The good news is that there are plenty of online software solutions that can help you with everything from assigning tasks and setting deadlines, to tracking progress and sharing files and information.</p><p>For <strong>file-sharing and organization</strong>, <a href="http://drive.google.com/">Google Drive</a>, <a href="https://www.dropbox.com/">Dropbox</a> and <a href="https://products.office.com/en-us/onedrive/onedrive-for-business">Microsoft OneDrive</a> are all great options that allow you to sync files across devices and back them up in a secure environment. It is important to find the best option for your company and stick with it, so as to avoid the confusion of having files distributed across platforms.</p><p>As for <strong>Project Management software</strong>, popular options include <a href="https://basecamp.com/">Basecamp</a>, <a href="https://www.atlassian.com/software/jira">Jira</a>, <a href="https://trello.com/en/teams">Trello</a> and <a href="https://clubhouse.io/">Clubhouse</a>. Such tools come with great organizational capabilities that ultimately translate into productive collaboration. There are plenty of great platforms out there, but again, it is important to do your research and select one that best responds to the needs of your company.</p><p>Technology is a great facilitator and it has helped businesses come a long way, but it is not a substitute for strategy. Defining clear processes and procedures is vital for the success of your project management action plan.</p><p><strong>3. Productivity</strong></p><p>How do we measure — and improve — productivity in the workplace? This is probably the most daunting question businesses are faced with when transitioning to a remote environment. Quantifying productivity can be rather tricky, as it requires defining clear performance metrics and methods.</p><p>Many companies fall into the trap of micromanaging, but that approach is more likely to kill productivity, rather than support it. A better alternative is to set up a system that measures performance through results and focuses on project outcomes.</p><p>On a more positive note, data show that working remotely can tremendously improve productivity among employees.</p><p>Many factors come into play, but there’s one in particular that seems to carry special weight, namely the ability to focus without interruptions.</p><p>What’s more, face-to-face interruptions are by far the most common and the most disruptive, mainly because they are impossible to ignore. According to a <a href="https://www.ics.uci.edu/~gmark/chi08-mark.pdf">study from the University of California Irvine</a>, it takes an average of 23 minutes and 15 seconds to regain focus and get back on track after a distraction. As it turns out, <a href="https://www.washingtonpost.com/gdpr-consent/?next_url=https%3a%2f%2fwww.washingtonpost.com%2fnews%2finspired-life%2fwp%2f2015%2f06%2f01%2finterruptions-at-work-can-cost-you-up-to-6-hours-a-day-heres-how-to-avoid-them%2f">losing focus can cost you as much as 6 hours of productivity per day</a>.</p><p>Although working from home comes with its own set of challenges and distractions, it certainly accounts for fewer face-to-face interruptions.</p><p>Remote work ultimately translates into autonomous employees who have the freedom to optimize their schedules and environment for maximum productivity.</p><p><strong>4. Trust</strong></p><p>The last and probably most important aspect of building a remote-first company culture is trust. Giving your employees a sense of autonomy and ownership increases morale and productivity, thus creating an overall positive work environment.</p><p>It may be tempting to try to control each aspect of what your team does throughout the workday, but micromanagement has been proven to be the least effective management style. This approach ends up destroying trust and hindering productivity in the workplace.</p><p>Instead, allow your employees to prove themselves trustworthy and capable of self-management. You’ll find that most people are intrinsically motivated to perform well and deliver high-quality work. Make it a priority to build a culture of trust and support and success will follow.</p><p><strong>Final Thoughts</strong></p><p>The Coronavirus outbreak is changing how — and where — we work. Companies all over the world are developing strategies towards building a remote-first work environment.</p><p>For businesses to survive, we need to understand the implications of the crisis and adapt on the fly to uncertain conditions. But more importantly, we need to start looking out for each other, protect our employees and foster a high-trust culture where innovation and success can thrive regardless of the circumstances.</p><p><em>Written by </em><a href="https://medium.com/u/a13cc1ebad0c"><em>Alexandra Efrimov</em></a><em> and </em><a href="https://medium.com/u/21ec7e5a2daf"><em>Alexandru Lazar</em></a><em>.</em> <em>Originally published at </em><a href="https://mcro.tech/adopting-a-remote-first-company-culture/"><em>https://mcro.tech</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54d75d47e860" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mcro/adopting-a-remote-first-company-culture-in-the-time-of-coronavirus-54d75d47e860">Adopting a remote-first company culture in the time of Coronavirus</a> was originally published in <a href="https://medium.com/mcro">MCRO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outsourcing — Why, When and Where?]]></title>
            <link>https://medium.com/mcro/outsourcing-why-when-and-where-f330aa3599f3?source=rss-a13cc1ebad0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f330aa3599f3</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[outsourcing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Alexandra Efrimov]]></dc:creator>
            <pubDate>Mon, 08 Jul 2019 12:44:24 GMT</pubDate>
            <atom:updated>2019-07-08T12:45:17.386Z</atom:updated>
            <content:encoded><![CDATA[<h3>Outsourcing — Why, When and Where?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TAu_RXTcCEgb8UKltfi_-w.png" /></figure><p>Digitisation is changing the business world. Entire industries are being disrupted and reinvented as we speak. In order to thrive in this dynamic world, companies must be agile and take advantage of digital opportunities at every turn.</p><p>Success in today’s business environment is <strong>driven by innovation</strong> and “out of the box” thinking. With this in mind, more and more companies choose to outsource services and reach out to experts in different areas. This allows businesses to <strong>increase their efficiency</strong> and to focus on their niche while still getting support from specialists.</p><h3>Why outsourcing is the way forward</h3><p>Outsourcing has gained a lot of ground over the last few years and it is expected to continue to <strong>grow and gain popularity</strong> across different sectors. Amongst the most commonly outsourced functions are the ones pertaining to IT. More and more companies looking for <strong>cost-efficient solutions</strong> choose to develop their software overseas. And I say cost-efficient because lately the focus has shifted to <strong>“quality over quantity”</strong>, meaning that cutting costs is no longer the main reason for decentralising activities. Sure, outsourcing allows for significant cost savings, but it also means improved core business focus and flexibility in use of resources, access to a <strong>world-class talent pool</strong>, and the list can continue.</p><h3>Why Romania is the new outsourcing hotspot</h3><p>The go-to ITO destination for companies looking for high-quality, yet affordable work is <strong>Europe</strong>. More exactly, <strong>Central and Eastern Europe (CEE)</strong> are increasingly popular options when it comes to outsourcing software development.</p><p>The majority of countries that fall under the CEE region are ranked amongst the <strong>top rated destinations for outsourcing</strong>. Given their reputation for high quality work, advanced technical skills and proficiency in English, this comes as no surprise. Countries such as Ukraine, Poland and Romania are highly ranked on <strong>HackerRank and TopCoder</strong>.</p><h3>1. Highly Qualified IT Professionals</h3><p>Romania is said to have one of the largest populations of certified IT specialists in Europe. With a pool of about 100,000 professionals in various IT-related niche segments, <strong>it ranks 1st in Europe and 6th worldwide</strong>.</p><p>One of the main reasons for this is the Romanian educational system. Not only does it do a great job in preparing the next generation of software developers, but it also provides the necessary environment for labor market integration.</p><p>Since the IT sector is one of the highest paying in Romania, more and more programmes that strengthen the relationship between companies and universities are being implemented every year. IT companies organise internships and workshops in schools and universities as a way to attract top talent.This of course benefits both parties, as students get firsthand know-how from IT professionals.</p><p>As for the education system itself, some say the <strong>standards of academic excellence</strong> and the rigour of the curricula are reminiscent of the country’s history of communism, special importance being attached to science, mathematics and technology.</p><p>More than 60% of the people working in the IT sector are <strong>computer science majors</strong>.</p><h3>2. Cost-Efficiency</h3><p>Let’s talk money. <strong>Eastern Europe</strong> is known for its competitive prices, so if you’re looking to cut costs and still get high quality services, look no further.</p><p>As opposed to outsourcing to India, China or the Philippines, prices here fall under the moderate range. But let’s be honest, <strong>quality work</strong> costs money and outsourcing to the cheapest bidder has its own type of price.</p><p>We’re talking from experience when we’re saying that hiring a team from a bargain destination is like playing the lottery — the odds are not in your favor. Have a look at the following article presenting some statistics on the matter: <a href="http://newobserveronline.com/95-of-it-engineers-in-india-incapable-new-report-reveals">http://newobserveronline.com/95-of-it-engineers-in-india-incapable-new-report-reveals</a></p><p>That being said, you can still save money and <strong>get great results</strong>. Romanian developers might not be the cheapest on the market, but the price-quality ratio justifies the investment.</p><p>Outsourcing is no longer all about cutting costs. As mentioned before, during the past few years there has been a global shift towards cost-effectiveness. Cheap labor is not compatible with an innovation <strong>driven culture of quality.</strong></p><p>Romania is an ideal destination for clients looking to balance quality and cost.</p><h3>3. Multilingual Communication</h3><p>Romania’s <strong>multilingual culture</strong> is another one of the aspects that make it one of the top destinations for outsourcing.</p><p>According to the <a href="https://www.ef.com/wwen/epi/regions/europe/romania/">EF English Proficiency Index</a>, Romania ranked #16 in the world with a <strong>high English language proficiency</strong>. Besides being proficient in English, Romanians are also known to speak <strong>French, German, Italian and/or Spanish</strong>.</p><p>Foreign languages are taught in schools, meaning that by the time they graduate college, most Romanians are fluent in at least two languages.</p><p>Communication is vital when establishing any kind of business relationship. <strong>Successful communication</strong> leads to successful projects, therefore language proficiency should be one of the main reasons affecting the destination for outsourcing services. This ensures that both parties are on the same page and that all goals, expectations and requirements are <strong>clearly stated and understood</strong>.</p><p>The vast majority of Romanian developers are proficient in at least one foreign language, meaning that it comes natural for them to <strong>communicate clearly and effectively</strong> with clients abroad.</p><h3>4. Culture and Mentality</h3><p>Apart from the language barrier, another common issue affecting business relationship is related to cultural gaps. Differences in cultural background, values and traditions might seem harmless at a first glance, but they can have a notable impact on an outsourcing engagement.</p><p>Romania shares a lot similarities with the <strong>western culture</strong>, making it a great choice for companies in Europe and USA looking to outsource.</p><h3>5. Business Environment</h3><p>Romania is widely recognised as one of the <strong>top quality ITO providers in Europe</strong>. With a <strong>stable IT sector growth</strong> rate, it has attracted investors all over the world, especially after joining the European Union in 2007.</p><p>The presence of <strong>global high tech companies</strong> such as Microsoft, IBM, Oracle, Intel, Amazon, Emerson and National Instruments confirm that Romania is nothing less than <strong>a hidden outsourcing gem.</strong> It’s no wonder that Romanian is the second most spoken language in the <strong>Microsoft offices</strong>.</p><h3>6. Blockchain / ETH</h3><p>Romanians have been part of the blockchain space since its beginning by contributing to <strong>the core development of projects</strong> such as Bitcoin, Ethereum, Cardano, Cosmos, Zilliqa and Aion. Their contribution includes launching their own projects (e.g. IPSX, Elrond, Sether) and supporting tools like the Moonlet Wallet, as well as building blockchain developer communities.</p><p>Having experienced communism not so long ago, it comes as no surprise that Romanian devs jumped right into a <strong>censorship resistant technology</strong>. This is one of the reasons why Romania is <strong>one of the most concentrated resources for blockchain development</strong>.</p><h3>Conclusion</h3><p>Romania has gained its reputation of being a <strong>great ITO destination</strong> thanks to its major tech hubs, large talent pool and affordable prices. Romanian developers <strong>are highly skilled in a wide array of technologies, multilingual and open-minded</strong>. If you’re looking to work with passionate and professional individuals who are known for their “out of the box” thinking and ability to deliver great results, <strong>you’re in luck</strong>. You have reached your destination.</p><p><strong>Looking for highly skilled devs?</strong> <a href="https://mcro.tech/contact/">Let’s get in touch.</a></p><p><em>Originally published at </em><a href="https://mcro.tech/outsourcing-why-when-where/"><em>https://mcro.tech</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f330aa3599f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mcro/outsourcing-why-when-and-where-f330aa3599f3">Outsourcing — Why, When and Where?</a> was originally published in <a href="https://medium.com/mcro">MCRO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to run a successful Design Sprint]]></title>
            <link>https://medium.com/mcro/how-to-run-a-successful-design-sprint-1ecc0d11bdf5?source=rss-a13cc1ebad0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ecc0d11bdf5</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alexandra Efrimov]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 13:55:28 GMT</pubDate>
            <atom:updated>2018-11-16T15:13:42.055Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9jJOcQpdBwDuVjR36l7mg.png" /></figure><h3>How to Run a Successful Design Sprint</h3><p><a href="https://www.statista.com/statistics/271644/worldwide-free-and-paid-mobile-app-store-downloads/">Statistics</a> point out that by 2021 the total number of app downloads will reach a remarkable 258 billion. While this is impressive, most people end up using only a handful of apps on a regular basis. The question here is, how do you set yourself apart in such a competitive market? The answer is innovation. We want innovative digital products, and we want to build them faster. In order to keep up with the fast-paced digital world, we need to rethink the way we approach product design. Enter Design Sprints — a problem solving methodology that allows us to go from ideation to prototyping and testing in as little as 5 days. Impressive, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/0*pErjebPExOm-03gz.jpg" /></figure><h4><strong>So what is a Design Sprint?</strong></h4><p>Most of you might be familiar with the “sprint” concept from Agile software development, where it refers to a set period of time during which specific work has to be done and submitted for review. Similarly, the Design Sprint is a timebox which concentrates the focus of the product team around a specific problem-solving goal.</p><p>The methodology was developed at GV (Google Ventures) as a way to help companies solve problems and test ideas fasters. Each Design Sprint consists of 5 distinct phases:</p><ul><li>Day 1: Understand</li><li>Day 2: Sketch</li><li>Day 3: Decide</li><li>Day 4: Prototype</li><li>Day 5: Validate</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*n9Idlr2yWhJVCKOk.jpg" /><figcaption>Image Source: <a href="http://gv.com/sprint/">GV Design Sprint</a></figcaption></figure><h4><strong>Set the Stage</strong></h4><p>The first step of the process is planning the sprint and laying the foundation for success. At this point it’s all about defining the challenge, selecting the right people and creating the proper environment for problem solving.</p><ul><li><strong>Define the challenge</strong></li></ul><p>An important and often overlooked part of setting the stage is defining the problem. Making sure everyone is on the same page and that the scope of the sprint is crystal clear will greatly increase the rate of success.</p><ul><li><strong>Put together the sprint team</strong></li></ul><p>The next thing we need to focus on is putting together a team of experts in different areas of the business. The nature of the required expertise might vary from project to project, but it is important to have a diverse skill set readily available for each step of the process. Ideally, your sprint team will be comprised of no more than 7 members.</p><ul><li><strong>Assign key roles</strong></li></ul><p>Two key roles that should be assigned are those of the Decider and the Facilitator. The Decider is the one who calls the shots when it comes to settling debates and making final decisions about what goes into the prototype. The Facilitator is responsible with managing the overall sprint by keeping the team energized and ensuring everything goes as planned.</p><ul><li><strong>Prepare the environment</strong></li></ul><p>Lastly, a suitable work-environment should be prepared for the week that follows. We want the team to focus on the challenge rather than dealing with administrative duties. This means booking a sprint room for the week, preparing the right equipment and providing necessary office supplies. That being said, don’t skimp on sticky notes. Now that the stage has been set, it’s time to kick off the sprint.</p><h4><strong>1. Monday: Define the Challenge</strong></h4><p>Monday is about choosing the target for the sprint and further defining the challenge. We want to make sure everyone involved in the process is on the same page and understands the problem and the purpose for solving it. The team needs to agree on a long-term goal and create a map of potential risks and challenges that might arise in the process. We want sprinters to play a game of “good cop, bad cop” in order to define the happy path and highlight the desired outcome without overlooking possible adversities. Simply put, what we want is to map out the problem, paving the way for the following days. Next, the focus should be on creating a shared vision and knowledge base among team members. Given the tight deadline the team is facing, it is important to prioritize and organize information so as to avoid wasting time and effort throughout the sprint.</p><h4><strong>2. Tuesday: Find Solutions</strong></h4><p>While Monday was about the challenge, Tuesday is all about the solutions. This stage of the sprint is basically an ideation-driven process of sketching out possible solutions. Each team member contributes by roughly sketching his/her ideas on sticky notes and then submitting them anonymously. The purpose is to generate a broad range of ideas and then to narrow them down into actual solutions that will become the building blocks of the prototype.</p><h4><strong>3. Wednesday: Make Decisions</strong></h4><p>Wednesday is dedicated to decision making. Now that we have sketched our way to a pool of ideas, it’s time to discuss and evaluate. The team goes through each and every sketch, discussing and remixing ideas until solutions begin to take shape. Once the winning ideas take surface, the next step is creating a storyboard. This stage is meant to provide a step-by-step plan for prototyping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*z7AQ-cDSXSPCL_HL.jpg" /></figure><h4><strong>4. Thursday: Prototype</strong></h4><p>On Thursday the team works on turning the storyboard into a realistic, testable prototype. We want to include just enough detail so as to convey the main idea and features. Given that the final result will be put in front of real customers on Friday, we want the right amount of fidelity to ensure we get the best results from testing. This step of the process also includes getting ready for the following day, meaning that we want to review the prototype, confirm the schedule and prepare the interview scripts for the testers.</p><h4><strong>5. Friday: Test</strong></h4><p>On Friday it’s time to put our ideas to the test. By now we should have a tangible prototype ready to be tested with real customers. The process involves conducting 1:1 interviews with 5 users, either in person or remotely. By observing how they interact with our prototype, we’ll be able to get immediate, authentic feedback, allowing us to understand what works and what doesn’t. This valuable information is going to save us a lot of time and resources in the long run. Friday’s results will set the direction for the product and will reveal our next step in the process.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FBDagLpxFIm3SM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FBDagLpxFIm3SM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FBDagLpxFIm3SM%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/da438b86e75ffc4a9d28fac2b39e06f4/href">https://medium.com/media/da438b86e75ffc4a9d28fac2b39e06f4/href</a></iframe><h4><strong>Conclusions</strong></h4><p>Design Sprints provide a framework for sketching, prototyping and testing any digital product lightning fast. The final prototype might not be readily available for development, but it does allow us to understand what works and what doesn’t in a short amount of time. Investing 5 days into testing an idea will provide actionable insight and will eventually save you a lot of time and resources. This is one of the quickest ways to innovate and validate your ideas while reducing the risks commonly associated with product design.</p><p><em>Originally published at </em><a href="https://mcro.tech/design-sprint/"><em>mcro.tech</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ecc0d11bdf5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mcro/how-to-run-a-successful-design-sprint-1ecc0d11bdf5">How to run a successful Design Sprint</a> was originally published in <a href="https://medium.com/mcro">MCRO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Atomic Design Systems]]></title>
            <link>https://medium.com/mcro/introduction-to-atomic-design-systems-9e5557c7775?source=rss-a13cc1ebad0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e5557c7775</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[atomic-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Alexandra Efrimov]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 10:54:35 GMT</pubDate>
            <atom:updated>2018-10-17T12:22:11.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*avQt9Id785Vu90Xbs2_Fnw.png" /></figure><p>We live in a digital world, and the need to design complex interfaces that function effectively across different screen sizes and environments has changed the way we approach design.</p><p><strong>Enter Atomic Design</strong></p><p><strong>Atomic design</strong> is a methodology for creating elaborate design systems. Originally coined by Brad Frost, the methodology has its roots in <strong>Modular Design</strong> and it essentially refers to breaking down complex interfaces into basic, reusable components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AE5MK5CldfENbdTLjjtCgw.png" /></figure><p>The five stages of atomic design, as formulated by Brad Frost, are <strong>Atoms, Molecules, Organisms, Templates</strong> and finally, <strong>Pages</strong>.</p><p>In the natural world, <strong>atoms</strong> are the basic building block that make up all matter. The atomic elements of our interfaces translate into basic HTML elements, such as form labels, inputs, buttons and so on. These can’t be broken down any further without losing functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-Y8riNw8opCXWr3mQtmJA.jpeg" /></figure><p>Atoms further combine to form <strong>molecules</strong>. These compounds take on new properties as a result, allowing them to complete specific functions. In the context of design, a text field, a label and a button combine together to form a search field molecule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BGUDXXx8EVJ4gUEiDYOlUQ.jpeg" /></figure><p>In the same manner, atoms and/or molecules combine together to form <strong>organisms</strong> — complex elements that represent specific sections of an interface. For example, a logo atom combined with a search form molecule and a primary navigation molecule form a basic page header.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUkiXmlwqR4rddEa2grNww.jpeg" /></figure><p><strong>Templates</strong> provide the basic layout by defining the underlying content structure of a page.</p><p><em>“You can create good experiences without knowing the content. What you can’t do is create good experiences without knowing your content structure. What is your content made from, not what your content is.”</em> — Mark Boulton</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsen7wVsVqCqvE-6mD5qQw.jpeg" /></figure><p>The <strong>pages</strong> are the actual output of the process — they are representative of how the final interface looks like with real content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXjAlRmqZtQ3VjcItGUONw.jpeg" /></figure><p>Although constructed in a hierarchical manner, the process is not of a linear nature. The focus is on the cohesive whole, encouraging maintaining a holistic view of the product throughout the process, but also on the basic building blocks of which the product is comprised. It’s important to focus on individual components to establish their function and form, but this has to be done in the context of the final UI.</p><p><strong>The Advantages of Atomic Design</strong></p><p>There are numerous advantages to adopting the atomic mental model and applying it to your workflow.</p><ol><li><strong>Time Efficiency</strong> — It allows for design and development teams to create complex products faster and more efficiently. Having a library of readily available components means faster and easier prototyping. Moreover, it also allows for easy modifications that reverberate across the system as a whole.</li><li><strong>Reusability</strong> — Provides an inventory of UI components and design solutions that can be combined and applied throughout the product, not having to reinvent the wheel every time a feature request rises.</li><li><strong>Consistency</strong> — Promotes consistent design vocabulary and cohesive user experience.</li><li><strong>Manageability</strong> — Establishing a centralized design vocabulary means everybody speaks the same language. This translates into greatly improved team collaboration and project manageability. This is especially advantageous for large-scale projects which involve bigger teams.</li></ol><p><strong>Conclusion</strong></p><p>Atomic design is a methodology for design systems that was developed in response to the constantly and rapidly evolving digital world. It provides a framework for creating complex interfaces that work well across different devices and screen sizes. Atomic design translates into team efficiency, manageable projects, consistent and cohesive user experience and more importantly, higher quality products.</p><p><em>Sources:</em></p><p><a href="http://atomicdesign.bradfrost.com/">http://atomicdesign.bradfrost.com/</a></p><p><a href="https://vimeo.com/179245570">https://vimeo.com/179245570</a></p><p><em>Originally published at </em><a href="https://mcro.tech/atomic-design/"><em>mcro.tech</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e5557c7775" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mcro/introduction-to-atomic-design-systems-9e5557c7775">Introduction to Atomic Design Systems</a> was originally published in <a href="https://medium.com/mcro">MCRO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>