<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Information Sharing on Keisuke Hattori</title><link>https://httrksk.github.io/tags/information-sharing/</link><description>Recent content in Information Sharing on Keisuke Hattori</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 23 Jul 2026 03:00:00 +0900</lastBuildDate><atom:link href="https://httrksk.github.io/tags/information-sharing/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Do Teams Duplicate Work That Sharing Could Prevent?</title><link>https://httrksk.github.io/post/20260723/</link><pubDate>Thu, 23 Jul 2026 03:00:00 +0900</pubDate><guid>https://httrksk.github.io/post/20260723/</guid><description>&lt;h4 id="background">Background&lt;/h4>
&lt;p>Anyone who works in a team has had the experience of discovering that a teammate has been doing the same work, without either of them knowing. The remedy is simple: say which task you intend to take on. Shared workspaces, project-management systems, and Slack are all available, and a single message reaches everyone. Yet sharing is still neglected, and duplicate work does not go away.&lt;/p></description></item></channel></rss>