<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>03069nam a22004451i 4500</leader>
  <controlfield tag="001">000706837</controlfield>
  <controlfield tag="003">CaToSAGE</controlfield>
  <controlfield tag="005">20240202172226.0</controlfield>
  <controlfield tag="005">20230109140345.7</controlfield>
  <controlfield tag="006">m     o  d</controlfield>
  <controlfield tag="007">cr un|||||||||</controlfield>
  <controlfield tag="008">230109s2022    enk    fo     000 0 eng d</controlfield>
  <datafield tag="STA" ind1=" " ind2=" ">
   <subfield code="a">NEZPRACOVANÝ IMPORT</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">9781529622881 :</subfield>
   <subfield code="c">No price</subfield>
   <subfield code="q">(ebook)</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(OCoLC)1362533314</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">CaToSAGE</subfield>
   <subfield code="b">eng</subfield>
   <subfield code="e">rda</subfield>
   <subfield code="e">pn</subfield>
   <subfield code="c">CaToSAGE</subfield>
   <subfield code="d">UtOrBLW</subfield>
  </datafield>
  <datafield tag="050" ind1=" " ind2="4">
   <subfield code="a">HD2731</subfield>
   <subfield code="b">.S29 2022</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2="4">
   <subfield code="a">338.74</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Sawhney, Mohanbir S.,</subfield>
   <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Nike :</subfield>
   <subfield code="b">tiptoeing into the metaverse /</subfield>
   <subfield code="c">Mohanbir Sawhney, Pallavi Goodman.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
   <subfield code="a">London :</subfield>
   <subfield code="b">Kellogg School of Management,</subfield>
   <subfield code="c">2022.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">1 online resource.</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
   <subfield code="a">text</subfield>
   <subfield code="b">txt</subfield>
   <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
   <subfield code="a">computer</subfield>
   <subfield code="b">c</subfield>
   <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
   <subfield code="a">online resource</subfield>
   <subfield code="b">cr</subfield>
   <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="490" ind1="1" ind2=" ">
   <subfield code="a">SAGE business cases</subfield>
  </datafield>
  <datafield tag="520" ind1="8" ind2=" ">
   <subfield code="a">Throughout 2021, excitement about the metaverse as the next generation of the internet experience had been building steadily. The buzz reached a fever pitch in October 2021, when the CEO of Facebook, Mark Zuckerberg, announced that the company was changing its name to Meta and that it would spend $10 billion to build &quot;the metaverse.&quot; Nike had been exploring opportunities in this new virtual environment with several experimental probes, including its purchase of a virtual sneaker company called RTFKT, partnerships with game platforms Roblox and Fortnite, the creation of blockchain-based digital sneakers called CryptoKicks, and moves to protect its brands and logos by filing for trademarks for its virtual sneakers and logos. In its early metaverse initiatives, Nike had employed a &quot;probe and learn&quot; strategy to evaluate the metaverse as a new channel for customer engagement and to create new digital revenue streams. However, it was now time for Nike to define a cohesive metaverse strategy that would help drive its business goals. To do this, Nike's digital team needed to understand how each of the metaverse initiatives would help Nike to grow revenue, build brands, and promote its thought-leadership position as an innovator. The team then needed to prioritize these initiatives by assessing their risks, rewards, and reversibility. Finally, it needed to define a roadmap to scale and enhance each initiative. In charting its course in the metaverse, Nike also needed to consider whether the timing was right to place big bets on metaverse platforms and assets, given the high level of uncertainty about the evolution of this emerging space.</subfield>
  </datafield>
  <datafield tag="588" ind1=" " ind2=" ">
   <subfield code="a">Description based on XML content.</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="7">
   <subfield code="a">elektronické knihy</subfield>
   <subfield code="7">fd186907</subfield>
   <subfield code="2">czenas</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="9">
   <subfield code="a">electronic books</subfield>
   <subfield code="2">eczenas</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Corporations</subfield>
   <subfield code="x">Technological innovations.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Metaverse.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Goodman, Pallavi,</subfield>
   <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="830" ind1=" " ind2="0">
   <subfield code="a">SAGE business cases.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="3">SAGE Knowledge</subfield>
   <subfield code="u">https://sk.sagepub.com/cases/tiptoeing-into-the-metaverse</subfield>
   <subfield code="y">Plný text</subfield>
  </datafield>
  <datafield tag="BAS" ind1=" " ind2=" ">
   <subfield code="a">SBC</subfield>
  </datafield>
  <datafield tag="BAS" ind1=" " ind2=" ">
   <subfield code="a">EB</subfield>
  </datafield>
  <datafield tag="993" ind1=" " ind2=" ">
   <subfield code="x">NEPOSILAT</subfield>
   <subfield code="y">EB</subfield>
  </datafield>
 </record>
</collection>
