<?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 Pavel Morshenyuk on Medium]]></title>
        <description><![CDATA[Stories by Pavel Morshenyuk on Medium]]></description>
        <link>https://medium.com/@pavelmorshenyuk?source=rss-f1da637e46a2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wHij7SQCa0-DyRH6NpqSCg.png</url>
            <title>Stories by Pavel Morshenyuk on Medium</title>
            <link>https://medium.com/@pavelmorshenyuk?source=rss-f1da637e46a2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:28:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pavelmorshenyuk/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[Improving Dev-Department’s Motivation Using Ship-It Days]]></title>
            <link>https://medium.com/@pavelmorshenyuk/improving-dev-departments-motivation-using-ship-it-days-8fbfac198f7e?source=rss-f1da637e46a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fbfac198f7e</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Pavel Morshenyuk]]></dc:creator>
            <pubDate>Tue, 20 Mar 2018 17:02:38 GMT</pubDate>
            <atom:updated>2018-03-20T17:02:38.865Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1tN4glr1pc4paZ8Pd-bnw.jpeg" /></figure><p>Motivation of employees is always an important topic for every company. Why? Because with a right motivation three persons in your company can easily do the same amount of work as five persons in another company.</p><p>There are different ways of improving motivation:</p><ul><li>Money — various bonuses and competitive salaries</li><li>Promotions and titles — make a person to stand out from the others, give him or her a special title like “Head of Web Services Architecture” (good title effect can last quite long)</li><li>Team-building — going to the bar together, bowling, darts or some outdoor events</li></ul><p>… and many others, but today we are going to have a look on Ship-It day approach, which is more specific to software development teams.</p><h3>What is the Ship-It day?</h3><p>I am not sure who was the first to introduce such kind of thing, but a lot of people pointing towards Google. Idea is simple — give your team one day to work on anything they like:</p><ul><li>Play with a new programming language or framework</li><li>Investigate some third-party software tool that can be used during day-to-day work</li><li>Think about different concepts of UI and UX design of the existing company’s application or some new app</li><li>Build a new tool that eliminates some office problem or brings people from different departments together</li></ul><p>This list is of course incomplete, but you have got a general idea, right?</p><h3>Why is the Ship-It day?</h3><p>If you are a line manager, team lead, CTO or CEO, you might want to ask me: “Why the hell we should spend time and money on dev team to play with their toys?”.</p><p>Well, you will be surprised, but this simple thing can bring your company quite a lot of benefits, and motivation of the team is just a side-effect. I have worked in several companies through out my career and I am really happy that all of them ended up introducing Ship-It days in a one way or another. Now I would like to show you a few examples of what you can get if you start practicing Ship-It days today.</p><h4>New product ideas</h4><p>Every employee has something in mind about current company’s products, including software developers. Developers maybe have no insights from market reports, business trends and marketing analytics, but they have nice, strange and sometimes crazy ideas. Give them some time and you can have a new product prototype that will conquer the hearts of your customers and investors.</p><p>It could happen that 90-99% of their ideas will be not successful, but the rest, with some love from marketing and sales departments, could make you king of the hill. Try to google about history of GMail for instance.</p><p>And now just imagine a motivation of the person whose idea was accepted by the company and his boss and became a part of the company’s product portfolio!</p><h4>Productivity</h4><p>Typically there is always no time for development of some automation tools to speed up development, testing or deployment when you are in a middle of the process. Ship-It day could be a good solution for that.</p><p>In my team, for example, during the Ship-It day we have introduced a quake-like console to our web application for administrators, where any developer can add a new CLI command to automate some routines. For testing of some business process we reduced the testing time from 20 minutes to 5, because command automates multiple steps of the process that are not relevant for the test-case.</p><p>Another developer played with Visual Studio Team Services (VSTS) and managed to automate deployment to the cloud. Not everything at once and she needed a help from her peers, but this allowed us to get rid of dozens of manual steps during deployments. At the end instead of 4 persons and 4 hours, live deployment takes only one person and one and a half hours (manual work is about 15 minutes actually).</p><p>One more example could be a billboard preview module for the main application. Developer wanted to get into Canvas and HTML5, and he decided to build a preview tool where you can upload any billboard photo from the street, mark the area of the billboard and select an image to be displayed. Yes, you can do the same with Photoshop and Paint.net, but now it is easier and built-in into the main app. Managers love it!</p><p>Developers got rid of the boring tasks by automation, investigated new technologies and introduced something useful for the rest of the team — motivation is raising again!</p><h4>Innovation</h4><p>Since new technologies and frameworks are involved Ship-It day has a big amount of innovation potential. It could be a missing step for your team to finally stop using their beloved framework from the stone age and switch to something new and shiny: modern stack, multi-platform support, community support, less code to maintain and etc.</p><p>Last Ship-It day one of the developers combined together Voice Recognition services and Text Translation services from Microsoft Azure and built a very nice app for our monthly meetings. Company is based in Germany and these meetings a held in German, so some of our fresh members of the team who came from all over the world are struggling with understanding. This simple app is a big step in uniting the company together and improving team motivation!</p><h3>Ground rules</h3><p>In order to make Ship-It day successful there should be some ground rules. These rules were gathered by me throughout the years, but you can feel free to remove or amend some of them or bring new ones.</p><h4>One day only</h4><p>It is important to keep it within one day. Developers will beg you to extend it to several days or a week. In this case it will be quite a big investment and since outcome of the Ship-It day is not always super useful — management could be disappointed.</p><h4>Fixed target</h4><p>The target of the Ship-It day work should be discussed and agreed during the meeting before day starts. Manager can correct the direction of the planned work and make it more relevant for current company’s goals and strategy. Also, without it, person could jump from one task to another and deliver nothing by the end of the day.</p><h4>Deliverable</h4><p>It is really important to have something delivered by the end of the day. Without deliverable something — it is a waste of time and frustration.</p><p>Too much to do? Try to reduce scope of the task and deliver just a prototype or try to find another team-member to help you with this project.</p><p>Deliverable could be anything — including an article in your Wiki about a new technology or framework with an overview where it could be used in the project, what are the pros and cons and comparison with the competitors.</p><h4>Demo and retrospective</h4><p>Do not forget to have a demo after the Ship-It day and include somebody from another department or somebody from the management team.</p><p>First of all it is an appreciation of the work.</p><p>Second — it is a good chance to get a feedback from non-developers, check the potential of the product, maybe even put it to the main road-map and write down the next steps in development.</p><h3>No-ideas day</h3><p>It could happen that some members of the team has no ideas for their Ship-It day: they tried everything last time, they are just shy or million other reasons…</p><p>In this case we call it Open Door day. Developers themselves or product owner or product manager can go to another departments like sales, marketing or accounting and ask them if they have something missing for their work:</p><ul><li>A tool to download excel files from remote FTP every morning</li><li>A smart calculator that will query several sources and prepare a report every week</li><li>A simple app to generate standard orders based on few input parameters</li><li>A webcam in the kitchen with a simple neural network to indicate when coffee machine is not busy</li><li>etc…</li></ul><p>Each idea should have a “Sponsor” — a person who suggested it. Developer can then work with the sponsor and deliver something nice by the end of the day which will make both of them happier.</p><h3>Conclusion</h3><p>Do not forget to organize Ship-It days regularly, for example every month or every second month — it should be enough to keep your development team in a good mood.</p><p>Do not make too often — lack of ideas could have a negative effect.</p><p>Do not force people to participate — this day should be powered by the person himself or herself, by his or her motivation and curiosity.</p><p>I really hope that this article will make you want at least to try the Ship-It day in your team. And once you tried — you are going to stick with it forever.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fbfac198f7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>