<?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>Fri, 01 May 2026 04:36:02 +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>Why Founders Who Hire on &#8216;Vibes&#8217; Scale Blind Spots</title>
		<link>https://grosum.com/blog/founders-hiring-vibes-blind-spots/</link>
					<comments>https://grosum.com/blog/founders-hiring-vibes-blind-spots/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Fri, 01 May 2026 04:36:02 +0000</pubDate>
				<category><![CDATA[Employee Engagement]]></category>
		<category><![CDATA[Performance Management]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/founders-hiring-vibes-blind-spots/</guid>

					<description><![CDATA[<p>Why Founders Who Hire on &#8216;Vibes&#8217; Just Scale Their Own Blind Spots Early-stage founders often rely on intuition to make their first few hires. It&#8217;s understandable. You&#8217;re building something personal, and you want people who &#8216;get it.&#8217; But when you&#8217;re hiring on &#8216;vibes,&#8217; you&#8217;re more likely to scale your own blind spots than your company. [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/founders-hiring-vibes-blind-spots/">Why Founders Who Hire on &#8216;Vibes&#8217; Scale Blind Spots</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/founders-hiring-vibes-blind-spots/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Why Your 360 Survey Has 30% Redundant Questions and What It Costs You</title>
		<link>https://grosum.com/blog/360-survey-redundant-questions-costs/</link>
					<comments>https://grosum.com/blog/360-survey-redundant-questions-costs/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Thu, 23 Apr 2026 12:57:53 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Continuous Feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/360-survey-redundant-questions-costs/</guid>

					<description><![CDATA[<p>Why Your 360 Survey Has 30% Redundant Questions and What It Costs You Imagine spending six figures on a 360 feedback survey, only to discover that 30% of the questions are redundant. That&#8217;s thousands of dollars and countless hours wasted, producing data that clouds the insights you desperately need. If you&#8217;re an HR leader, this [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/360-survey-redundant-questions-costs/">Why Your 360 Survey Has 30% Redundant Questions and What It Costs You</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/360-survey-redundant-questions-costs/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Why Your 360 Feedback Should Dictate Leadership Training</title>
		<link>https://grosum.com/blog/360-feedback-dictate-leadership-training/</link>
					<comments>https://grosum.com/blog/360-feedback-dictate-leadership-training/#respond</comments>
		
		<dc:creator><![CDATA[Rajarshi]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 04:51:12 +0000</pubDate>
				<category><![CDATA[360 feedback]]></category>
		<category><![CDATA[Employee Development]]></category>
		<category><![CDATA[Employee Engagement]]></category>
		<guid isPermaLink="false">https://grosum.com/blog/360-feedback-dictate-leadership-training/</guid>

					<description><![CDATA[<p>Stop Buying Leadership Training Until Your 360 Data Dictates the Curriculum Last year, a mid-sized tech firm spent $500,000 on leadership training programs. Six months later, employee surveys revealed no significant change in leadership effectiveness. Why? Because the training curriculum was based on industry trends, not the unique needs highlighted by their own 360 feedback [&#8230;]</p>
<p>The post <a href="https://grosum.com/blog/360-feedback-dictate-leadership-training/">Why Your 360 Feedback Should Dictate Leadership Training</a> appeared first on <a href="https://grosum.com/blog">GroSum Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://grosum.com/blog/360-feedback-dictate-leadership-training/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<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>
	</channel>
</rss>
