<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01446nam a22002537a 4500</leader>
  <controlfield tag="003">OSt</controlfield>
  <controlfield tag="005">20260511122924.0</controlfield>
  <controlfield tag="008">260428b        |||||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">0017-8012</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">TBS</subfield>
    <subfield code="b">EN</subfield>
    <subfield code="c">TBS</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Lorange, Peter</subfield>
    <subfield code="9">26949</subfield>
    <subfield code="e">author</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">How to design a strategic planning system</subfield>
    <subfield code="c">/ Peter Lorange, Richard F. Vancil.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="b">Harvard Business Review,</subfield>
    <subfield code="c">1976</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">75&#x2013;81 pages.</subfield>
  </datafield>
  <datafield tag="490" ind1=" " ind2=" ">
    <subfield code="a">Harvard Business Review</subfield>
    <subfield code="v">vol. 54, no.5</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Every business carries on strategic planning, although the formality of that process varies greatly from one company to the next. Conceptually, the process is simple: managers at every level of a hierarchy must ultimately agree on a detailed, integrated plan of action for the coming year; they arrive at agreement through a series of steps starting with the delineation of corporate objectives and concluding with the preparation of a one- or two-year profit plan. However, the design of that process&#x2014;deciding who does what, when&#x2014;can be complex, and it is vital to the success of the planning effort.</subfield>
  </datafield>
  <datafield tag="630" ind1=" " ind2="0">
    <subfield code="a">B2 PBT Business and Ecosystem Analysis (BiM)</subfield>
    <subfield code="9">26906</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Economics</subfield>
    <subfield code="9">2587</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Planning</subfield>
    <subfield code="9">731</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Vancil, Richard F.</subfield>
    <subfield code="9">26950</subfield>
    <subfield code="e">author</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://research-ebsco-com.hub.tbs-education.fr/linkprocessor/plink?id=af84d095-5f7b-3d95-9261-d771cd29a566</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">lcc</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">CT</subfield>
    <subfield code="a">TBS</subfield>
    <subfield code="b">TBS</subfield>
    <subfield code="d">2026-05-11</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2026-05-11</subfield>
    <subfield code="u">https://research-ebsco-com.hub.tbs-education.fr/linkprocessor/plink?id=af84d095-5f7b-3d95-9261-d771cd29a566</subfield>
    <subfield code="w">2026-05-11</subfield>
    <subfield code="y">ARTICLE</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">5435</subfield>
    <subfield code="d">5435</subfield>
  </datafield>
</record>
