<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>GroSum Blog</title>
	<atom:link href="https://grosum.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>https://grosum.com/blog/</link>
	<description>Its all about Employee Performance Management</description>
	<lastBuildDate>Wed, 08 Apr 2026 13:02:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://grosum.com/blog/wp-content/uploads/2017/02/cropped-g19-32x32.jpg</url>
	<title>GroSum Blog</title>
	<link>https://grosum.com/blog/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Unlocking 360 Feedback: The Power of Open-Ended Responses</title>
		<link>https://grosum.com/blog/unlocking-360-feedback-power-open-ended-responses/</link>
					<comments>https://grosum.com/blog/unlocking-360-feedback-power-open-ended-responses/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Wed, 08 Apr 2026 13:02:53 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/unlocking-360-feedback-power-open-ended-responses/</guid>

					<description><![CDATA[<p>Unlocking 360 Feedback: The Power of Open-Ended Responses In a 360 feedback cycle at a global firm, 9,600 open-ended responses were collected. They captured raw, specific insights — yet went unanalyzed. Thousands of words, the richest data available, gathered dust. The Problem with Ignoring Open-Ended Responses Organizations often focus on quantitative data from 360 feedback, [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/unlocking-360-feedback-power-open-ended-responses/">Unlocking 360 Feedback: The Power of Open-Ended Responses</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/unlocking-360-feedback-power-open-ended-responses/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Real Reason Employees Overlook Their 360 Feedback</title>
		<link>https://grosum.com/blog/real-reason-employees-ignore-360-feedback-2/</link>
					<comments>https://grosum.com/blog/real-reason-employees-ignore-360-feedback-2/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Wed, 01 Apr 2026 10:05:43 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<category><![CDATA[Employee Engagement]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/real-reason-employees-ignore-360-feedback-2/</guid>

					<description><![CDATA[<p>The Real Reason Employees Overlook Their 360 Feedback 87% of 360 feedback reports are opened once and then shelved. Employees skim them for an average of 11 minutes before they become digital dust collectors. It&#8217;s not a problem of attention; it&#8217;s a problem of relevance. The Problem with 360 Feedback Reports The typical 360 feedback [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/real-reason-employees-ignore-360-feedback-2/">The Real Reason Employees Overlook Their 360 Feedback</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/real-reason-employees-ignore-360-feedback-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Transforming 360 Feedback into Organizational Bench Strength</title>
		<link>https://grosum.com/blog/transforming-360-feedback-organizational-strength/</link>
					<comments>https://grosum.com/blog/transforming-360-feedback-organizational-strength/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Tue, 24 Mar 2026 05:56:28 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<category><![CDATA[Performance Review]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/transforming-360-feedback-organizational-strength/</guid>

					<description><![CDATA[<p>Translating 360 Feedback from Individual Reports to Organizational Bench Strength Imagine this: Your company just completed a 360 feedback cycle. 5,000 employees, 1,200 reports, and 48,000 data points. Each report, a 40-page behemoth. The result? A stack of PDFs, untouched by most, left to gather dust. Meanwhile, the question remains: How do these individual insights [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/transforming-360-feedback-organizational-strength/">Transforming 360 Feedback into Organizational Bench Strength</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/transforming-360-feedback-organizational-strength/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Decoding 360 Feedback: The Prompt Every Manager Needs</title>
		<link>https://grosum.com/blog/decoding-360-feedback-prompt-manager/</link>
					<comments>https://grosum.com/blog/decoding-360-feedback-prompt-manager/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Mon, 16 Mar 2026 07:08:01 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<category><![CDATA[Employee Engagement]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/decoding-360-feedback-prompt-manager/</guid>

					<description><![CDATA[<p>Decoding 360 Feedback: The Prompt Every Manager Needs A 360 feedback report lands on a manager’s desk. It&#8217;s 40 pages long, filled with data that took weeks to gather and analyze. Despite this, there&#8217;s only a 22% chance they&#8217;ll act on it in a meaningful way. Why? Because they don&#8217;t have the exact prompt to [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/decoding-360-feedback-prompt-manager/">Decoding 360 Feedback: The Prompt Every Manager Needs</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/decoding-360-feedback-prompt-manager/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Why the 360 Feedback Industry is Stuck in 2005</title>
		<link>https://grosum.com/blog/why-the-360-feedback-industry-is-stuck-in-2005/</link>
					<comments>https://grosum.com/blog/why-the-360-feedback-industry-is-stuck-in-2005/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Fri, 06 Mar 2026 07:26:03 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<category><![CDATA[Employee Engagement]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/why-the-360-feedback-industry-is-stuck-in-2005/</guid>

					<description><![CDATA[<p>Why the 360 Feedback Industry is Stuck in 2005 Last year, a survey of 1,200 organizations revealed that over 75% of HR leaders believe their 360 feedback processes are outdated. If you’re among them, you’re not alone. The 360 feedback industry is stuck in 2005, and it’s costing you valuable insights. The Problem: A Snapshot, [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/why-the-360-feedback-industry-is-stuck-in-2005/">Why the 360 Feedback Industry is Stuck in 2005</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/why-the-360-feedback-industry-is-stuck-in-2005/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
