<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remote Work on Trayix</title><link>https://trayix.com/tag/remote-work/</link><description>Recent content in Remote Work on Trayix</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 04 Nov 2020 09:00:00 +0000</lastBuildDate><atom:link href="https://trayix.com/tag/remote-work/index.xml" rel="self" type="application/rss+xml"/><item><title>Collaboration platforms: fewer tools, clearer rules</title><link>https://trayix.com/2020/11/collaboration-platforms/</link><pubDate>Wed, 04 Nov 2020 09:00:00 +0000</pubDate><guid>https://trayix.com/2020/11/collaboration-platforms/</guid><description>&lt;p&gt;When offices closed this spring, teams grabbed whatever worked. Zoom for meetings, Microsoft Teams for chat, Slack for another group&amp;rsquo;s chat, email for everything else, and a different board for each project. It was the right call at the time. Eight months later, many teams are paying for it: people check five places before they find the answer, and nobody is sure where a decision was made.&lt;/p&gt;&#10;&lt;p&gt;The fix isn&amp;rsquo;t another tool. It&amp;rsquo;s fewer tools and clearer rules.&lt;/p&gt;</description></item><item><title>Remote governance without micromanagement</title><link>https://trayix.com/2020/07/remote-governance/</link><pubDate>Wed, 15 Jul 2020 09:00:00 +0000</pubDate><guid>https://trayix.com/2020/07/remote-governance/</guid><description>&lt;p&gt;Several months into remote work, many leaders miss something they never noticed they had: a feel for how projects were going. They used to see who was in early, who looked worried, and who was huddled around a whiteboard. Without that, some compensate by adding status meetings, demanding daily reports, or installing software that tracks activity. It&amp;rsquo;s an understandable reaction. It&amp;rsquo;s also the wrong one.&lt;/p&gt;&#10;&lt;h2 id="why-surveillance-fails"&gt;Why surveillance fails&lt;/h2&gt;&#10;&lt;p&gt;Counting hours online or keystrokes measures presence, not progress. Good people notice quickly, and they respond by looking busy. Meanwhile the real signals, such as a blocked dependency or a risk growing quietly, stay hidden. More status meetings have a similar effect: they consume the time people need to do the work, and they rarely surface bad news any faster.&lt;/p&gt;</description></item><item><title>Running projects when everyone is remote</title><link>https://trayix.com/2020/04/running-projects-remotely/</link><pubDate>Wed, 08 Apr 2020 09:00:00 +0000</pubDate><guid>https://trayix.com/2020/04/running-projects-remotely/</guid><description>&lt;p&gt;A few weeks ago, most of your team worked in the same building. Now they&amp;rsquo;re at kitchen tables, spare bedrooms, and the occasional ironing board, and you&amp;rsquo;re still expected to deliver. If you lead projects, you didn&amp;rsquo;t get a chance to plan for this. Here&amp;rsquo;s what we&amp;rsquo;ve seen work for teams that moved to fully remote delivery almost overnight, using ordinary tools and a calm approach.&lt;/p&gt;&#10;&lt;h2 id="set-a-rhythm-and-keep-it-short"&gt;Set a rhythm, and keep it short&lt;/h2&gt;&#10;&lt;p&gt;In an office, a lot of coordination happens by accident: a question at someone&amp;rsquo;s desk, a comment in the hallway. Remote work removes those moments, so replace them on purpose. A short daily check-in of 10 to 15 minutes is enough for most teams. Ask three things: what moved, what&amp;rsquo;s next, and what&amp;rsquo;s in the way. Keep the video on if people can manage it, but don&amp;rsquo;t make it a rule. Not everyone has reliable bandwidth.&lt;/p&gt;</description></item></channel></rss>