<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>The paradox of implementing the government performance and results act: top-down direction for bottom-up implementation</title>
  </titleInfo>
  <name type="personal">
    <namePart>Long, Edward</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Franklin, Aimee L.</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xu|</placeTerm>
    </place>
    <dateIssued>2004</dateIssued>
    <issuance>continuing</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">ng </languageTerm>
  </language>
  <physicalDescription>
    <extent>p.309-19.</extent>
  </physicalDescription>
  <abstract>Research on the implementation of the Government Performance and Results Act generally has not considered how the strategic plan, annual performance plan, and annual performance report are produced and used. Are the documents good decision and management tools, as the act intends, or are agencies internalizing them to meet the unique needs of their organization? Interviews with representatives of 14 cabinet-level federal agencies suggest that implementation of the act is not standardized. Instead, it is influenced by the unique challenges that agencies face. Further, there is a relationship between the implementation challenges and the overall use of the documents. - Reproduced.</abstract>
  <subject>
    <topic>Public administration</topic>
  </subject>
  <relatedItem type="host">
    <name>
      <namePart>Public Administration Review</namePart>
    </name>
  </relatedItem>
  <recordInfo>
    <recordCreationDate encoding="marc">180718</recordCreationDate>
  </recordInfo>
</mods>
