<?xml version="1.0" encoding="UTF-8" ?>
<modsCollection xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" xmlns:slims="http://slims.web.id" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd">
<mods version="3.3" id="48742">
 <titleInfo>
  <title>Forced ranking</title>
 </titleInfo>
 <typeOfResource manuscript="no" collection="yes">mixed material</typeOfResource>
 <genre authority="marcgt">bibliography</genre>
 <originInfo>
  <place>
   <placeTerm type="text">Boston, Massachusetts</placeTerm>
   <publisher>Harvard Business School Press</publisher>
   <dateIssued>2005</dateIssued>
  </place>
 </originInfo>
 <language>
  <languageTerm type="code"></languageTerm>
  <languageTerm type="text"></languageTerm>
 </language>
 <physicalDescription>
  <form authority="gmd"></form>
  <extent>xiii, 260 p. : index. ; 24 cm.</extent>
 </physicalDescription>
 <note>&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;This is a comprehensive how-to guide to designing and implementing a &#13;
fair and effective forced ranking system, including how to accurately &#13;
categorise A, B and C players, and manage and reward players &#13;
differently. It clears away the confusion surrounding a controversial &#13;
performance management practice called forced ranking, which evaluates &#13;
how well employees perform relative to their peers instead of against &#13;
predetermined performance goals. More importantly, it provides a &#13;
tactical, how-to guide for doing forced ranking right - and highlights &#13;
the huge advantages firms and their employees can reap by doing so.&lt;/div&gt;&lt;br&gt;</note>
 <note type="statement of responsibility"></note>
 <classification>FCK</classification>
 <identifier type="isbn">0591397480</identifier>
 <location>
  <physicalLocation>Perpustakaan - Sekolah Tinggi Manajemen PPM Pusat Informasi Manajemen</physicalLocation>
  <shelfLocator>FCK Gro</shelfLocator>
 </location>
 <recordInfo>
  <recordIdentifier>48742</recordIdentifier>
  <recordCreationDate encoding="w3cdtf">0000-00-00 00:00:00</recordCreationDate>
  <recordChangeDate encoding="w3cdtf">2019-01-23 00:00:00</recordChangeDate>
  <recordOrigin>machine generated</recordOrigin>
 </recordInfo>
</mods>
</modsCollection>