<?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 Bogdan Litescu on Medium]]></title>
        <description><![CDATA[Stories by Bogdan Litescu on Medium]]></description>
        <link>https://medium.com/@bogdan.litescu?source=rss-6a915dca50e4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dS8WKF0PJ2_3riOKuKVcSg.jpeg</url>
            <title>Stories by Bogdan Litescu on Medium</title>
            <link>https://medium.com/@bogdan.litescu?source=rss-6a915dca50e4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:45:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bogdan.litescu/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[Unpacking Low-Code]]></title>
            <link>https://uxdesign.cc/unpacking-low-code-de577db5efbe?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/de577db5efbe</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Thu, 19 May 2022 10:37:37 GMT</pubDate>
            <atom:updated>2022-05-19T10:37:37.871Z</atom:updated>
            <content:encoded><![CDATA[<p>The past few years have exposed critical flaws in ageing IT infrastructures, accelerating the need for digital transformation. Furthermore, there is a growing expectation to provide seamless digital services in a technology-driven world.</p><p>Organizations looking to drive their self-sufficiency, and address specific needs, are therefore seeking ways to create their own solutions. Having the capability to create in-house software is therefore increasingly desirable, and the demand more noticeable. A Gartner <a href="https://www.gartner.com/en/webinars/4008393/cio-strategy-manage-the-opportunities-risks-of-democratized-business-led-it">presentation</a> suggested that IT teams may be expected to create a brand-new solution every 8 weeks.<strong> </strong>However, certain IT woes can make this unrealistic. This includes ageing legacy systems, a scarcity of skilled developers, and a disparity between IT and management.</p><p>To overcome these challenges and create their own solutions, many organizations are embracing low-code development platforms. In this article, we’ll explore low-code’s place in the future of development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*AIuK-1ssdPpBsWFhRr1ODg.png" /></figure><h3><strong>What is Low-Code and No-Code?</strong></h3><p>In brief, low-code refers to visual software tools that let users create applications with reduced hand coding. Graphical interfaces and drag-and-drop components accelerate development, and increase accessibility. The streamlined experience means that more people can build applications, while professional developers could expect to develop a fully-fledged solution in just days.</p><p>Low-code is sometimes used interchangeably with no-code, yet there is a distinction. Low-code reduces the amount of code required, while no-code removes it entirely. This means that even those without a coding background — sometimes referred to as “citizen developers” — can start building their own applications. The drawback to no-code is that it tends to be more limited in scope, and the level of customization and scalability comparably restrictive.</p><p>Fortunately, business leaders do not need to choose between no-code and low-code, with Plant an App offering a hybrid approach. With both at your disposal, you typically have greater choice when looking to build solutions, leverage the skills of your teams, and modernize outdated legacy systems.</p><h3><strong>Solving Problems Through Low-Code</strong></h3><p>A hybrid low-code platform can build a multitude of applications — especially if that platform allows developers to plug in their own code, and draw on advanced API capabilities. From external facing portals to data analytics, organizations from various sectors can bolster their custom development. Let’s consider why this is.</p><h4><strong>Decreased Development Time</strong></h4><p>Forrester has valued low-code development platforms to be up to <a href="https://www.forrester.com/blogs/why-you-need-to-know-about-low-code-even-if-youre-not-responsible-for-software-delivery/">10 times faster</a> than traditional methods — other sources say even higher. What is certain though, is that the visual nature of low-code means developers can build and deploy applications faster. Modular tools and pre-built templates help remove the repetition of hand coding, helping to accelerate delivery.</p><p>Low-code also goes hand-in-hand with automation, which is increasingly being adopted to enhance development productivity, as well as reducing the number of mistakes and human-errors that happen during routine tasks.</p><h4><strong>Agile, Integrated and Scalable</strong></h4><p>The ability to rapidly develop applications allows organizations to react quickly, matching their operations to changing markets, continuously evolving customer requirements, and sudden regulatory thresholds. And while other SaaS solutions often work in silos, the right low-code platform can perform as a fully connected enabler of software development. In fact, Plant an App’s advanced API suite quickly lets developers integrate with third-party software and wider digital communities.</p><p>When partnered with cloud-native low-code platforms, organizations have more headroom to scale in line with their growth, with increased deployment and data storage options.</p><blockquote><strong>Out of all the ways of creating data-driven digital experiences, this is the most straightforward, approachable way of doing it. Moreover, it creates a structure that is flexible, extensible — there is no constraint to doing further development.<br> </strong>— Jim Everett, Development and Innovation, University of Strathclyde</blockquote><h4><strong>Empowering People</strong></h4><p>Although low-code platforms can be highly sophisticated, they will have their limitations in certain areas. Custom coding continues to be a core part of application building, and <a href="https://www.forbes.com/sites/forbestechcouncil/2021/10/14/the-rise-of-no-code-and-low-code-solutions-will-your-cto-become-obsolete/">Forbes</a> has even stated that “the future model of the software development process won’t be complete without developers.”</p><p>Rather than making developers obsolete, low-code is a tool that can save them time, and augment their regular coding practices. Flexible platforms allow developers to plug-in their custom code, adding scripting to the top of builds created using low-code.</p><p>In addition to empowering developers, low-code platforms enable non-technical users to create their very own applications. This democratizes the development of software for a larger category of people, with some solutions not requiring a single line of code. It is therefore also easier to onboard new employees, and draw upon a wider pool of talent when developing applications.</p><h4><strong>A Collaborative Workplace</strong></h4><p>A single development process, one that can be understood by both citizen and professional developers alike, can help bridge differences in technical knowledge. Graphical representations are easier to reference than complex coding languages, and more meaningful discussions can be had regarding the way an application is shaping up.</p><p>Sometimes though, barriers to collaboration can be physical. A Gartner survey revealed that <a href="https://www.gartner.com/en/newsroom/press-releases/2020-04-14-gartner-hr-survey-reveals-41--of-employees-likely-to-">41% of employees</a> will work remotely at least some of the time after the pandemic, with many adjusting to a hybrid work pattern. With low-code however,<strong> </strong>different users are able work simultaneously on a single module, even if they are operating in different parts of the world.</p><h4><strong>Greater Transparency Across Teams</strong></h4><p>When business users are given the means to create their own in-house solutions, they are less likely to outsource software without IT’s knowledge — also known as “Shadow IT.”<strong> </strong>Rather than simply leaving business-users to their own devices though, IT teams can set user permissions and administrator controls, monitoring application development from a platform-based view. This helps make collaborative development secure and transparent, mitigating the risk of security breaches and data loss.</p><h3><strong>Evaluating a Low-Code Platform</strong></h3><p>If partnering with a low-code platform, one of your first questions should be who will be using it, and what they plan to develop. Some platforms will still require skilled developers, while others will be too simplistic to build enterprise-grade applications with. For this reason, platforms that offer both no-code and low-code functionality may be the safest, most versatile option. Additionally, vendors that offer transparent price points (and an included list of features) can make it easier to ascertain a platform’s value proposition.</p><p>It is also important to know if a low-code platform is able to integrate with your existing systems, along with other third-party software that you may wish to connect with going forward.<strong> </strong>A platform should be able to accommodate your upward curve as a business, such as introducing more users, or upscaling functionality.</p><p>Consider choosing vendors that demonstrate they have a long-term strategy and a constantly evolving platform. This could include regular updates, a growing asset library, or opportunities to speak with product experts. Platforms with active communities that share resources and knowledge can also be a good indicator of success.</p><h3><strong>Migration And Modernization</strong></h3><p>Modernizing legacy systems can be a complex process. Often heavily entrenched in an organization&#39;s architecture, replacing them could be a serious investment. However, cloud-native low-code offers organizations the ability to upgrade legacy systems on a gradual basis, with three different core migration paths offering more options and flexibility.</p><p>No matter which path you choose, adopting a low-code platform is an apt way of future-proofing your business. While legacy architectures can quickly become a hindrance, low-code doesn’t share the same risk of becoming obsolete. A low-code platform does not have to completely replace existing systems either; they can often work effectively alongside other architectures, and be used where necessary.</p><h3><strong>Final Thoughts</strong></h3><p>Where traditional development methods are too slow or cumbersome to keep up with a high demand for new software, low-code presents an opportunity to rapidly create in-house solutions. Developers are empowered to do more with their time, and organizations can draw on a wider range of talent across the board.</p><h4><strong>Disclaimer</strong></h4><p>I’m Founder and CEO at Plant an App, which is a comprehensive application development platform, where low-code and no-code combine to bolster traditional programming. Both business users and professional developers are empowered to create sophisticated software, faster and without friction. Built upon a decade of development knowledge — and fueled by a community of passionate low-code developers — Plant an App has helped a host of organizations upgrade their digital services. And with the most flexible pricing options of any low-code platform, our partners can choose exactly what software capabilities they want, with no hidden costs.</p><p>For more information, please visit <a href="https://www.plantanapp.com/">www.plantanapp.com</a>, or take a look at our in-depth <a href="https://whitepaper.plantanapp.com/?v=3.1">white paper</a> to gain a deeper knowledge of low-code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de577db5efbe" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/unpacking-low-code-de577db5efbe">Unpacking Low-Code</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[How to Never Miss a Single Email]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/how-to-keep-an-uncluttered-inbox-5ea018b4453e?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/1057/1*nBiEuBjfNR4SaH742GF7Dw.jpeg" width="1057"></a></p><p class="medium-feed-snippet">Having an uncluttered inbox is a good indicator for being productive, organized, pro-active and on top of everything that&#x2019;s going on.</p><p class="medium-feed-link"><a href="https://medium.com/swlh/how-to-keep-an-uncluttered-inbox-5ea018b4453e?source=rss-6a915dca50e4------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/how-to-keep-an-uncluttered-inbox-5ea018b4453e?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ea018b4453e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Wed, 19 Jun 2019 12:59:39 GMT</pubDate>
            <atom:updated>2019-06-20T10:29:46.886Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Anyone Can Code]]></title>
            <link>https://medium.com/swlh/anyone-can-code-1b5dee812658?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b5dee812658</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 11 Jun 2019 12:12:16 GMT</pubDate>
            <atom:updated>2019-06-12T07:49:51.609Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NQ4cntx-WPMMzIEI" /><figcaption>Photo by <a href="https://unsplash.com/@hiteshchoudhary?utm_source=medium&amp;utm_medium=referral">Hitesh Choudhary</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We’re living the times when being technology savvy and knowing how to code is becoming as fundamental as being able to read and write. Technology is all around us available in potentially infinite supply. It’s up to us to discover and put it to good use.</p><p>Therefore, the ability to manipulate technology is increasingly becoming a skill rather than a job. Instead of relying on programmers to mediate the act of telling the computers what to do, one can take the matter in own hands. In a highly competitive market, imagine the cost structure of a company that does everything by hand or outsources automation and computations compared to a company where consultants are able to perform most of the automation and computations themselves.</p><p>And it pays better too, because on one hand you have a huge<a href="https://chiefexecutive.net/think-talent-shortage-bad-just-wait/"> shortage of IT talent</a> that’s only going to get worse and, on the other hand, companies gain a lot in productivity by having the people that really understand the business requirements doing most of the coding.</p><blockquote><em>The good news is anyone can code.</em></blockquote><p>This article is the introduction of a longer series that aims to be a guide for acquiring technical skills that can be effectively used in day to day activities.</p><h3>Why You Should Learn Coding</h3><p>Being able to code allows automating part of the work so you can deliver better, faster or cheaper. At a personal level, learning how to code gives you more tools to address challenges. It will grow your business or result in better-paying jobs.</p><p>You’ll find that coding is not as much about logic and mathematics as it’s about creativity, intuition and free thinking. And most of all, it’s about confidence. Anyone can do it and anything is possible. In this sense, you’ll find it has more in common with life principles and methods.</p><h3>What Kind of Coder Are You?</h3><p>There are thousands of programming languages and coding frameworks out there. Rushing into things without first determining what flavour best suits you will likely lead to being overwhelmed and, ultimately, to lose confidence and interest in learning how to code.</p><p>My advice is to start with the things you enjoy doing in your everyday life. The idea is that you’d be able to put the newly acquired skills to use immediately. Having quick wins is likely to boost your motivation to continue your journey into coding.</p><p>I will define a few coding profiles by describing their behavioural patterns. Analyze how you relate to each of them. It’s normal to find yourself in more than one profile, but try to pick one to start with. You can always explore later. And you’ll find that in coding there is a lot of knowledge that is transferable to different technologies.</p><h4>The Visual Coder</h4><p>This person cares a lot about how things look and feel. No matter how good the information presented by a document is, if it’s not well formatted or it does not flow in an easy to grasp manner, this person will evaluate it as having poor quality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ioV_UINDjQWXI1MS" /><figcaption>Photo by <a href="https://unsplash.com/@maxcodes?utm_source=medium&amp;utm_medium=referral">Max Nelson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Good technologies to start with are<a href="https://www.w3schools.com/whatis/whatis_html.asp"> HTML</a> and<a href="https://www.w3schools.com/css/css_intro.asp"> CSS</a>. These can be applied to format website pages, emails and basically anything that runs inside a web browser. The learning path can continue with Javascript.</p><p>It’s probably also best to start with Photoshop or other image editors in parallel. Most of the times, it’s easier to draw and make modifications in this kind of applications before doing the coding.</p><h4>The Data Analyst</h4><p>To this individual, the world is described through data. Truth must always be backed by numbers. Data comes from many sources — could be collected on a website, from IoT sensors, inputted manually or imported from external sources. In either case, data usually comes in a raw format. It takes processing and visualisation to makes sense out of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L9F0qptejW3rUPid" /><figcaption>Photo by <a href="https://unsplash.com/@campaign_creators?utm_source=medium&amp;utm_medium=referral">Campaign Creators</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In some situations, the process of working with data is exploratory, for example, to find out what kind of customers a company has. Otherwise, the process is oriented towards achieving quantifiable results for a specific purpose.</p><p>Good technologies to start with are spreadsheets (Excel or Google Spreadsheets). By using formulas, macros, and charts one can process the raw data into meaningful numbers.</p><p>The next level is<a href="https://www.w3schools.com/sql/"> learning SQL</a>. I recommend Microsoft<a href="https://www.microsoft.com/en-us/sql-server/sql-server-editions-express"> SQL Express</a>, which is the free edition of the SQL Server. It’s easy to install and get started with and it comes with SQL Server Management Studio (SSMS) which is a powerful IDE to interact with the database.</p><p>This path also leads to state-of-art technologies. Think Artificial Intelligence or, more specifically, machine learning algorithms. These can be used to make predictions, automatical classification and discovering not so obvious relations between data.</p><h4>The Optimizer</h4><p>The world is not perfect. But that doesn’t stop the optimizer from aiming towards it by identifying problems and coming up with ways to address it. This individual is process driven. A good process is something that can be reproduced over and over again with similar results. And, more importantly, a good process can be constantly acted upon in order to apply iterative improvements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XgtsbZ9-cqEvA91z" /><figcaption>Photo by <a href="https://unsplash.com/@darwiiiin?utm_source=medium&amp;utm_medium=referral">Darwin Vegher</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The start for the optimizer it’s tricky as it varies widely on applicability domain. A good starting point is not in the realm of code, but in understanding how software applications are designed and work. I also recommend my previous article on<a href="https://medium.com/swlh/using-spreadsheets-for-prototyping-a17f011109d0"> Using Spreadsheets for Prototyping</a>.</p><p>The Optimizer will explore technologies that help with the digital transformation and process automation. There are numerous tools out there that automate parts of processes. In order to use them effectively, I find the most important skill is the ability to understand how<a href="https://code.tutsplus.com/tutorials/a-beginners-guide-to-http-and-rest--net-16340"> HTTP and Web APIs</a> work. A very good tool besides curl, which is mentioned in the tutorial I linked above,<a href="https://www.guru99.com/postman-tutorial.html"> Postman</a> is a much more user-friendly tool to start with.</p><p>There are infinite possibilities on how one can use external APIs to improve processes. A simple use case is to call APIs from external services to import data in spreadsheets which otherwise would have had to be filled in manually. Or use Google Translate API to automatically translate a document. Or call a machine learning API to automatically do recognize objects in images and put them in specific folders.</p><p>Ultimately, Robotic Process Automation (RPA) software such as<a href="https://www.uipath.com/"> UI Path</a> or low code development platforms for business processes such as<a href="https://plantanapp.com/"> Plant an App</a> are key in driving digitalization and automation initiatives. They allow custom processes to be automated without having to code everything.</p><h3>Knowledge is Abundant</h3><p>I dare to say 50% of the work of a programmer is finding answers on the internet. The most effective ways to search for information related to code is through Google Search and<a href="https://stackoverflow.com/"> Stack Overflow</a>. There are a lot of self-taught programmers out there to support this statement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lnzAB8lkFdnzNyip" /><figcaption>Photo by <a href="https://unsplash.com/@lysanderyuen?utm_source=medium&amp;utm_medium=referral">Lysander Yuen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s generally accepted by developers that if something can’t be found on the internet, it either means that they’re doing something wrong or that the search is not accurate.</p><p>Learning how to search is gained by experience. Until one develops the vocabulary and knowledge, I advise using learning platforms for discovering the semantics of each technology. There are numerous good tutorials out there. Just to mention a few that I know personally, there’s<a href="https://www.udemy.com/"> Udemy</a>, C<a href="https://www.coursera.org/">oursera</a>, and<a href="https://codemy.com/"> Codemy</a>.</p><h3>The Right Mindset</h3><p>Anyone can code. However, not anyone will become a top programmer. And one rarely needs to become one.</p><p>The purpose of learning how to code is not to change your line of work, but to become better at what you’re already doing in your everyday life.</p><p>So, think about what value coding would bring about what you do. This will set you a direction. Once you have that, the next step is to make a plan. If you don’t reserve time on a regular basis, it’s not likely you will learn how to code. If your employer allows it, reserve 1 or 2 hours every day during regular office hours to learn. After a few weeks, you’ll be able to demonstrate to your team how the new skills help you do things better, faster or cheaper.</p><p>Finally, the most successful programmers I know have one thing in common. They are curious about how things work. Gaining a deep level of understanding develops intuition and the ability to extrapolate concepts that apply to other areas as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b5dee812658" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/anyone-can-code-1b5dee812658">Anyone Can Code</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Things Done]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/getting-things-done-69bad722c434?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/2600/1*3w_TVmoVRHmL3j_XDe-EpA.jpeg" width="3968"></a></p><p class="medium-feed-snippet">With so many distractions, it&#x2019;s becoming increasingly difficult to remain focused and get things done. This is my method to find balance.</p><p class="medium-feed-link"><a href="https://medium.com/swlh/getting-things-done-69bad722c434?source=rss-6a915dca50e4------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/getting-things-done-69bad722c434?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/69bad722c434</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 28 May 2019 15:32:42 GMT</pubDate>
            <atom:updated>2019-05-28T21:10:32.571Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Using Spreadsheets for Prototyping]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/using-spreadsheets-for-prototyping-a17f011109d0?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/2392/1*uZpYhpwGUPfLfvU0H72XsA.png" width="2392"></a></p><p class="medium-feed-snippet">Find why the spreadsheet is probably the best tool to communicate requirements to software developers.</p><p class="medium-feed-link"><a href="https://medium.com/swlh/using-spreadsheets-for-prototyping-a17f011109d0?source=rss-6a915dca50e4------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/using-spreadsheets-for-prototyping-a17f011109d0?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/a17f011109d0</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 14 May 2019 12:19:09 GMT</pubDate>
            <atom:updated>2019-05-15T09:19:54.156Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Role Based Recruitment Process]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bogdan.litescu/the-role-based-recruitment-process-4caf3dcdcae9?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/2600/0*uRtB4s1z8-kPJqzS" width="4208"></a></p><p class="medium-feed-snippet">In a highly competitive market for talent, democratizing the recruitment process leads to better hires.</p><p class="medium-feed-link"><a href="https://medium.com/@bogdan.litescu/the-role-based-recruitment-process-4caf3dcdcae9?source=rss-6a915dca50e4------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bogdan.litescu/the-role-based-recruitment-process-4caf3dcdcae9?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4caf3dcdcae9</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 05:51:53 GMT</pubDate>
            <atom:updated>2019-04-17T22:10:02.331Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Achieve Mindfulness by Offloading Thoughts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/achieve-mindfulness-by-offloading-thoughts-8c7fdff5a464?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/2600/1*fezUOa0Fj3jox83zcEuzAQ.jpeg" width="2976"></a></p><p class="medium-feed-snippet">We tend to have a lot on our mind that take us away from the present moment. Plus, we get new ideas all the time, some of which excite us&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/swlh/achieve-mindfulness-by-offloading-thoughts-8c7fdff5a464?source=rss-6a915dca50e4------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/achieve-mindfulness-by-offloading-thoughts-8c7fdff5a464?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c7fdff5a464</guid>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 09 Apr 2019 17:58:44 GMT</pubDate>
            <atom:updated>2019-05-16T15:55:19.002Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Networking for Introverts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bogdan.litescu/9-networking-tips-for-introverts-c9ad8b7f3849?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/2600/0*mb2ywb-_uf2hpYDl" width="4373"></a></p><p class="medium-feed-snippet">It was early in the morning. Besides the distant humming of an engine, everything was silent. In the mirror, a reassuring figure was&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@bogdan.litescu/9-networking-tips-for-introverts-c9ad8b7f3849?source=rss-6a915dca50e4------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bogdan.litescu/9-networking-tips-for-introverts-c9ad8b7f3849?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9ad8b7f3849</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[introvert]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 02 Apr 2019 11:22:16 GMT</pubDate>
            <atom:updated>2019-04-11T07:16:37.664Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Debugging — A Philosophical Approach]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bogdan.litescu/debugging-a-philosophical-approach-bf60d6626f6e?source=rss-6a915dca50e4------2"><img src="https://cdn-images-1.medium.com/max/2600/0*jxwbtRbqwatHi3gH" width="5760"></a></p><p class="medium-feed-snippet">An unique approach to finding truths about the nature of things and ourselves.</p><p class="medium-feed-link"><a href="https://medium.com/@bogdan.litescu/debugging-a-philosophical-approach-bf60d6626f6e?source=rss-6a915dca50e4------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bogdan.litescu/debugging-a-philosophical-approach-bf60d6626f6e?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf60d6626f6e</guid>
            <category><![CDATA[understanding]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 26 Mar 2019 09:52:05 GMT</pubDate>
            <atom:updated>2019-04-16T16:45:46.746Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Art of Having Productive Meetings]]></title>
            <link>https://medium.com/@bogdan.litescu/the-art-of-having-productive-meetings-df7c63d9d400?source=rss-6a915dca50e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/df7c63d9d400</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Bogdan Litescu]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 10:30:25 GMT</pubDate>
            <atom:updated>2019-03-24T12:04:16.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xdcKfvvF4Lo393l8" /><figcaption>Photo by <a href="https://unsplash.com/@thomasdrouaultphotography?utm_source=medium&amp;utm_medium=referral">Thomas Drouault</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I used to loathe meetings. Most of the people I knew felt more or less the same. It seemed such a waste of everyone’s time. The worse was around 10 years ago. I was part of a 5 man team delivering a project for a US customer. Every 2 weeks, we’d have a meeting with one of the owners which would last for 6 hours. Luckily, since we were all remote, we’d be able to do something other work during the meeting. Out of 6 hours, maybe 30 minutes was of interest to any particular participant. The respective company, although it had huge goals, failed to produce significant results.</p><p>Fast forward to present day, my team lives under the impression that I love meetings. Well, I’m not. I just got better as I’m motivated to make most of everyone’s time, including mine.</p><h3>Are meetings really necessary?</h3><p>In my mind, meetings were something that corporations afforded to do. I was focused on producing value. And values was difficult to produce.</p><p>The reasons? People in my team lacked a unified vision. Or I would delegate something only to find out it was done a different way or not done at all. Or I would take some decisions by myself that my guys would resent for. Or support tickets would get lost in the help center app. Or someone in the team would get frustrated at someone else that should have delivered, not knowing that something else came up.</p><p>Chaos is the best description. And I embraced chaos because I valued creativity so much. But instead of being creative, me and my team would spend our time reacting to the negative effects caused by chaos, putting out fires all over the place.</p><p>So how do you take decisions? How do you align everyone to the same vision? How do you make a plan? How do you create and improve a process? How do you inspire and create momentum?</p><p>Productive meetings.</p><p>I’ve been reading a lot about meetings and most of what I read felt without substance. Not that the information was poor. I guess they lacked first hand experience. So here it is. I’ll give you (almost) everything I know about having really productive meetings and explain them with real life situations and what happens if you miss to satisfy any of the criteria.</p><h3>1. Have Clear Objectives</h3><p>The first thing that a meeting should have is objectives. We don’t meet just for the sake of being in the same room.</p><p>We hold annual and quarterly meeting with the objective to set the priorities. We have monthly meeting for planning tasks that correspond to our priorities. We have a meeting every Monday morning to get each other up to date to what happened last week and plan the week ahead. We have a weekly support meeting with the stated objective to improve the support process and customer experience and review the effect of our actions on the KPIs. We have targeted meetings to find solutions to a problem or to brainstorm ideas. I have sync meetings with other managers.</p><p>Making sure that everyone knows the objectives makes it much easier to keep conversations from going off-topic. This is one of the main reasons for really long meetings.</p><p>Also, by communicating the objectives, you set the right expectations for the participants. They enter the meeting focused and with the mindset aligned to the objectives. They might already have thought some ideas prior the meeting that help reaching the objectives.</p><p>By the way, I found very good inspiration for holding regular meetings by reading <a href="https://scalingup.com/">Scaling Up</a> by Verne Harnish. As with any recommendation I make, take it with a grain of salt and only apply what resonates with you.</p><h3>2. Carefully Choose the Participants</h3><p>The natural tendency is to invite everyone that is involved in a way or another. I found this approach to lower the quality of a meeting. People that have a lower involvement relative to the objectives would easily get bored and stray away, affecting the general mood of the meeting.</p><p>One factor that I take into account is how much stake a participant has relative to the objectives. For example, if it’s a planning meeting, I would invite everyone that has a major role in executing the plan. Anything that we put on the table will transform into work that they will need to perform, so they are fully involved in the conversation, providing arguments, feedback and ideas. Whatever the plan that comes out of the meeting is, it belongs to everyone that was there.</p><p>At the support meeting we have the entire support team, as the changes we do to the process affect everyone. So we argue and we negotiate and in the end we decide on a few very specific tasks that need done until the next meeting.</p><p>Of course, if the support team was a lot bigger, I would have to reduce the number of participants. This brings me to the second set of criteria, which is diversity. For example, major business decisions we shape in the weekly management meeting, where the participants include the financial director, the operations manager and the technical lead. It provides sufficient diversity to see a problem from different angles and find the a satisfactory compromise.</p><h3>3. Schedule the Meeting</h3><p>From this perspective, there are two kinds of meetings: regular and one-time meetings. With regular meetings, it’s best to find the same day of week and same hour to hold them. This makes it much more comfortable for all participants to make the rest of their schedule. With some meetings, you might have to experiment different days and hours to find what works best. For example, we have a training meeting that used to be Wednesdays at 5pm. Often it happened that we had calls with US based customers at that time because of the timezone difference. On every training, there were a few team members that weren’t there.</p><p>With one time meetings there is a bit more friction. These usually pop-up during the week and they require a sync to communicate the objectives and find a time that works for everyone. I like to avoid unnecessary interruptions, as they greatly affect productivity. I found the best time to schedule these is just before or after lunch. But before arranging a one time meeting, ask yourself if it’s really necessary. Can the matter wait until the next regular meeting? Give yourself an honest answer. There’s a point beyond which having an additional unplanned meeting gives people the feeling of bureaucratization and inefficiency.</p><p>With any kind of meeting, I emphasize the importance of being on time. Every delay means that the meeting might fail to achieve its objectives or that someone might have to reschedule other meetings that follow. My experience is that meetings usually starts a few minutes late. One trick I read about is to schedule meetings at odd hours, for example 9:57 for the morning meeting. I haven’t tried this method yet as a few minutes are acceptable to me.</p><p>Finally, I strongly believe that having meetings that are longer than 1 hour are not productive. It will happen to last more than that, especially in the beginning as you learn to master the art of holding meetings. I will give you tips on how to keep meetings short later in this article.</p><h3>4. Prepare an Agenda</h3><p>The agenda is the blueprint of a meeting. Not having an agenda is like building a house without a schematic. And it’s not enough that an architect creates a schematic. It must also pass engineering calculations. That is a good agenda.</p><p>When I first start a regular meeting, I prepare a generic agenda that has three sections called <em>Retrospective</em>, <em>Topics </em>and <em>To Do</em>. There’s also a sheet with topic proposals to discuss in the next meeting. This is a very important element. During the week, you’ll get ideas. The first instinct is to arrange a meeting and share it with everyone. This interrupts people, decreasing their productivity. I don’t know about you, but I get a few dozen ideas every day while I’m at work. So, instead of bothering everyone, I put the idea on the <em>Proposals</em> list. Many times, I scratch a few of these at the beginning of next meeting as they don’t seem as such good ideas as they were when they first revealed to me.</p><p>During the regular meetings, I identify recurring themes and turn them into sections. For example, in the agenda of the Monday meeting, there is a section called <em>1001 Things to Do With Our Software</em>. This section was added out of necessity. The guy that runs this campaign is constantly looking for ideas. He used to get very frustrated that the team would not provide them when he asked around. So on Monday, by having everyone present and focused on conversation, we find inspiration in the work we did last week and add to the list. Now, we always have about 10 ideas sitting there, which solved the problem.</p><p>The idea is to get very specific and constantly adjust the agenda so it answers your present needs. If a problem pops up over and over again, making it a section in the agenda to discuss it every week is likely to solve it. If you find yourself skipping a section a few meetings in a row, it’s probably a good idea to talk about it if it still makes sense to discuss.</p><p>One final note on the agenda. As it gets very specific and structured, I recommend to keep a section that encourages open discussions. In my case, this is the <em>Topics</em> section. Anyone can come with subjects that are hot from the previous week. This section is the source of organically reshaping the agenda to match the current landscape.</p><h3>5. Designate a Facilitator</h3><p>The facilitator’s primary focus is not on providing input towards the meetings’s objectives, but to make sure the group as a whole reaches the objectives. It’s very important that this person is someone that people respect. It could be someone with good leadership capabilities, strong skills related to objectives or a manager.</p><p>The facilitator makes sure that everyone has a chance to speak and that arguments are exchanged in a non-conflictual manner. When the conversation goes off-topic, the facilitator proposes that the off-topic is noted down in the <em>Proposals</em> list of the meeting to be discussed in a future session. In fact, the off-topic could belong to a different meeting altogether as it often happens. In any case, the focus is returned to the main topic.</p><p>The facilitator keeps track of time, making sure all points on the agenda are touched. Where conversation on a topic is going on for too long, the facilitator leads the discussion towards intermediary conclusions. For example, it could be decided that two of the participants meet later during the week to decide on a very specific point that would help continue the conversation at next meeting. As the facilitator learns the art of coordinating a meeting, I recommend also keeping track on how much touching each section of the agenda takes, so at next meetings the facilitator knows when to direct the conversation to a conclusion so there’s still time for the rest of the points on the agenda.</p><p>Good facilitators know what questions to ask in order to challenge people to come up with arguments. But the best facilitators are the ones that cultivated the critical and creative thinking to the participants so, in time, they mostly mark moments in the agenda and watch out for off-topics. It sounds easy, but in reality it’s not. The facilitator has to construct a safe place where everyone can speak freely without fear of being judged. Then, the participants leave the meeting satisfied that they came up with something they couldn’t have conceived by themselves.</p><h3>6. Keep Minutes</h3><p>Before I started keeping minutes, I often found myself in situations where someone would say that we agreed to do things a certain way during the last meeting while I insisted that it has been decided differently. It was my word against theirs. What an absurd conversation to have. Was I absent in that meeting? Was I only thinking about it in a different way, ignoring what everyone else was saying?</p><p>By keeping minutes, one can always get back and check the actual facts. I believe that the level of details to put in the minutes would vary. In my case, I found that marking just the titles of the topics that were discussed, a bullet points of ideas and the conclusions is enough. On the other hand, for meetings in certain government areas, the minutes would probably have to be a literal transcript of the entire conversation. Try different levels of details to see what works for you. My advice is to aim for lowest level of detail that doesn’t lose clarity. This has the benefit that it’s easier to go through the minutes at a later time.</p><p>The goal is to have a clear picture of the meeting. If possible, the minutes should be kept by the facilitator. This way, it becomes a tool to track the conversation. Having the minutes in eyesight, the facilitator can go back to certain notes if they conflict with the direction the conversation is going.</p><h3>7. Output</h3><p>I would often say during the meetings that if we don’t produce any output, then the meeting was just wasted time. There are many reasons that would cause a meeting to lack output. It could be that the discussion is too generic, that people avoid to make commitments or that additional research is needed in order to have meaningful conversations.</p><p>The output is the measurable product of the objectives, therefore it should be clearly stated from the beginning to set the right expectations. If the meeting’s objective is to improve a process, then the output is a list of well defined tasks that are assigned and can be done until the next meeting.</p><p>The output can be a list of tasks, a plan, a document, a mock up, a budget, a process, a decision, a list of ideas and so on. In order to call the meeting productive, the output has to be of good quality. A meeting could go very well and produce a list of tasks which, for some reason, don’t get done. In this case, the meeting failed to provide value. I could put it in the wasted time category. But a much more productive approach is to investigate during the next meeting why the output was not of good quality and adjust.</p><h3>8. Recap</h3><p>The facilitator should reserve some time before wrapping up the meeting to briefly go over the output and make sure everyone is on the same page. Now is the time when some participants could realize that the output is too ambitious. After all, the output was built up from pieces during a 1 hour meeting. The facilitator can respond by reassigning ownership, looking for other resources to get involved, narrowing down the scope or challenging the participants to find solutions. It’s much more important to make constant progress than to make a huge effort once. In time, it adds up.</p><p>When the output is measured subjectively, I use an evaluation method during the recap. For example, at the end of our Monday planning meeting I ask each of the team member to represent on the scale of 1 to 10 how clear is what they need to do in the current week. This helps me understand if the meeting added clarity in each and everyone’s perception.</p><p>Besides output, it’s also good to mention the topics that were parked by the facilitator, so the participants have confidence that they will be discussed in one of the next meetings.</p><h3>9. Follow Up</h3><p>After the meeting ends, the facilitator needs to make sure that the everyone has access to the meeting minutes and the output. Additional actions might be required, for example to transfer the tasks in a task management application. There is no need for the facilitator to follow up until the next meeting to check that the participants have actually acted on executing the output. That should be the job of people that assumed responsibility.</p><p>From experience I learnt that in the beginning people will forget to act on the output. When confronted in the next meeting to investigate why, the participants will become more aware that the meeting is not just about producing an output, but executing it as well.</p><h3>What’s Next?</h3><p>I’m currently experimenting with speedy meetings. I allocate 25 minutes for a meeting which sets a faster pace. This interval might sound familiar. It’s what people usually use for time management with <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">Pomodoro</a>. Luckily, Google Calendar has built-in support for speedy meetings which make it easy to handle.</p><p>One final piece of advice I have for you: keep meetings at a minimum. Many topics can be addressed on the spot. In our office it happens quite a few times a day that a problem needs solving. People would send a message on Slack asking for someone’s input when they get some spare time. They meet around someone’s desk and make a decision. Planning a meeting would be a major overhead and would block the person needing input. Nearly all of our internal meetings are regular meetings. Once every two weeks it happens to have a spontaneous meeting to handle an exceptional situation.</p><p>I wish you productive meetings that create value!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df7c63d9d400" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>