Professional Documents
Culture Documents
Zara's Business Model and Competitive Analysis
Zara's Business Model and Competitive Analysis
Zara, the most profitable brand of Inditex SA, the Spanish clothing retail group,
opened its first store in 1975 in La Coruñ a, Spain; a city which eventually became
the central headquarters for Zara’s global operations. Since then they have
expanded operations into 45 countries with 531 stores located in the most
important shopping districts of more than 400 cities in Europe, the Americas,
Asia and Africa. Throughout this expansion Zara has remained focused on its
core fashion philosophy that creativity and quality design together with a rapid
response to market demands will yield profitable results. In order to realized
these results Zara developed a business model that incorporated the following
three goals for operations: develop a system the requires short lead times,
decrease quantities produced to decrease inventory risk, and increase the
number of available styles and/or choice. These goals helped to formulate a
unique value proposition: to combine moderate prices with the ability to offer
new clothing styles faster than its competitors. These three goals helped to shape
Zara’s current business model.
Value drivers for Zara are both tangible and intangible in the benefits that are
returned to all stakeholders. Tangibly, Inditex, the parent company of Zara, has
11.02% net margin on operations and their market capitalization (Equity –
market value) is €13, 981 (in thousands) in 2002. Their net working capital
(current assets – current liabilities) is €133 (in thousands) . Additionally, the
success of Zara can be demonstrated through their outstanding financial
performance. From 1996 to 2000, Inditex SA tripled their corporate profits and
in 2001, a year of overall economic downturn in the retail industry, Inditex SA
saw a 31% increase in profits. Intangibly, customer loyalty and brand
recognition have provided significant value to Zara. The number of consumers
they attract continues to rise and their brand is synonymous with the cutting
edge of fashion at affordable prices. The successful implementation of Zara’s
business model provides great value to stakeholders and differentiates their
business from their peers.
Competitive Advantage
Fundamental to Zara’s success is their commitment to rapid response in
customer trends in fashion, producing clothing often and with short life spans
(10 wears). Their commitment to this goal and the capabilities that they have
developed to achieve it, have provided significant competitive advantage to Zara
especially in the areas of product development, strategic partnerships and cost of
production, advertising and marketing, and information technology
infrastructure. The efficiencies and processes developed in these four functions
differ significantly from their competitors and stand out in providing additional
value and profitability to Zara.
Product Development
Zara’s unique approach to product development is instrumental to their success.
Zara gives store managers significant autonomy in both determining the
products to display in their stores and which to place on sale, and relaying
market research and store trends back to their headquarters in La Coruñ a. At
headquarters there are teams of commercials who take this information into
account to design and effectively plan and produce all of Zara’s products. Zara
maintains a design team of 200 people, all of which produce approximately
12,000 new styles per year for Zara. The process of obtaining market
information and relaying it to design and production teams expedites product
development by shortening the throughput time of a product to 3-4 weeks from
design to distribution. This process is very different from its competitors. Many
competitors rely on a small elite design team that plans both design and
production needs well in advance. Stores have little autonomy in deciding which
products to display or put on sale because Headquarters plans accordingly and
ships quantities as forecasted. Zara’s speed to market in product development
exceeds the capabilities of its competitors. This in itself provides additional value
to stakeholders, customers, and stores in producing quality clothing at affordable
prices .Zara’s product development capabilities are essential to Zara’s business
strategy and future success.
The key decision makers in the ordering process on the face of it are the store
managers and the commercials at the HQ. However, there are certain issues that
need to be addressed here. The store manager’s decision influence on the
replenishment of garments is limited to a single order (twice a week) based on
manually auditing the quantities required for the store. This information is
subsequently sent to the HQ. Although they are the decision makers in this case,
the order is still conditional. In the fulfillment phase of the operations, the
aggregated demand is ascertained and the supply is allocated according to past
performance of the various garments at the stores.
For the ordering of new garments, store managers have the same amount of
autonomy. However, a tailored order form (known as ‘the offer’) is first
transmitted to a PDA based on several factors such as garment availability,
regional sales patterns and forecasts. The store manager then determines what
should be ordered from this offer. It is therefore essential that there is effective
flow of information between the HQ and the distribution centers to ensure that
store managers receive correct offers. In every store the managers would divide
the offer into segments and delegate this to different employees. These
employees would then beam their segments after walking through the store
using their own PDA, to the store manager’s handheld device. It is important to
note here that this form arrives 24 hours before the order deadline, creating
substantial pressure. The manager is dependent on the input of the employees in
order to create an aggregated form (now called the ‘order’) that gets sent back to
the HQ. Therefore, the store managers has full control over what should be
ordered from the new garments, however, this is based on the initial filtering
which is conducted from the HQ. It is fair to conclude that the store manager is
the preliminary decision maker in the case of replenishment, but this is subject
to availability as the next paragraph will make clear. For new garments, the
preliminary decision lays in the hands of the HQ commercial groups, although
there is a heavy reliance on historical information from the store manager. The
store managers are then responsible for submitting orders that are considered
necessary for their stores.
In the case of fulfillment of the orders, the situation is somewhat different. Store
managers are not involved in the process, instead, another group of commercials
are responsible to meet the orders of the various stores. This is because the
infrastructure is currently set up in such a way that the store manager has no
overview of the consolidated demand of the stores in its area, and therefore
cannot make a rational interpretation of how much should be allocated to its
own store. It makes sense for a dedicated team to satisfy the orders according to
the aggregated demand and supplies of the inventory at the distribution center
in the area, however, a more information could offer some additional benefits. In
the case of a shortage in supply, the commercial team at the HQ determines
which stores have been most effective in selling an item recently in order to
assign the production to the right store. Again, since this is contingent upon the
local customer demands and ultimately local trends (past performance), the
store manager really does not have much control over the extent to which its
orders will be met. The true decision makers in this case are deemed to be the
commercials. It has to be noted, however, that the future production for each
Stock Keeping Unit (SKU – defined as garment + fabric + color +size) order is
determined in collaboration with the product managers. Based on discrepancies
in demand and supply for different areas, forecasts can be made in terms of how
much the demand will be and therefore how much needs to be produced. They
are also considered to be key players in this area, though not so much decision
makers. Product managers indirectly rely on the information provided by store
managers’ orders. In addition, the commercials in charge of the fulfillment would
occasionally ship samples that were not requested by the store managers. This
again suggests where the true decision power lies.
By analyzing the decision makers in all parts of the operations and the flow of
information, stronger conclusions can be drawn as to where information is
urgently required in order to streamline procedures. In the next section of this
paper, exactly what information that could prove to be useful will be discussed.
Since the entire supply chain relies on the subjective orders that are placed by
the store managers, the accuracy of this information is elemental to Zara’s
operations. This so-called ‘theoretical inventory’ is required in order to keep the
supply chain robust without leading to excess supply. In the current system,
store managers’ order information is taken to be sacred, and these figures are
subsequently used for shipment and production.
At the moment, store managers have to manually assess their inventory. This is a
relatively slow procedure and suggests that there is room for improvement.
Resources are wasted since managers’ are preoccupied with a somewhat
administrative task. Admittedly, this is done to ensure that the manager gains an
insight of the inventory so that correct decisions can be made for the quantities
that need to be replenished. Information would probably help to speed up this
process, so that the managers can focus on employees and customers, instead of
having to roam the shops twice a week. Similarly for new garments, store
managers currently have 24-hour window of opportunity in which, in
cooperation with employees, a breakdown of the required garments has to be
made. Again, this is not only time consuming since information needs to be
entered into a relatively small device, at the store level it is logistically a complex
procedure. Only this time, it is not only the manager who is distracted, it also a
part of the employees who are involved. This poses the question as to whether
the provided service to the customer is in any way offset by the complex
logistics, and if so, to what extent, for example, sales have been missed due to a
lack in assistance. At the moment, store managers have no clear idea of how
much inventory is at the distribution centers. Information could prove to be
useful for store managers to make ‘smarter’ orders. If store managers assure a
customers that a particular sold out garment is reordered and will arrive in two
days, the chance that it this order does not come through (due to a lack of
information from the distribution centers), could be potentially damaging for
Zara. Information from the distribution centers and from the production
facilities, for that matter, will give store managers a better overview of the
garment availability, in order to adjust their orders and pass on this information
on to the customers. This would overcome the current blind order system.
By and large, more, and more frequent information at the stores, production
facilities and distribution centers would allow Zara to match demand and supply
more closely. Efficiency within stores can be improved and in production and
fulfillment, the speed and chance of delivery can be improved. The result is a
tighter control of Zara’s operations allowing for more an even more proactive
approach. Fast changing and unpredictable tastes of its target customers would
be anticipated even sooner and would enable Inditex to have an even more
effective cost control in accordance with its overall corporate strategy. The next
question will explore how a new Operating System could patch the gaps that
have been identified thus far.
Zara and its IT partner have in the past opted to use DOS as their operating
system for all the applications of the company. DOS is considered to be an
outdated system and few companies are still using it. The question of changing
the OS has therefore been raised. It has been already acknowledged that staying
so far behind in terms of technology can be risky but changing an OS in 531
shops would not be without risks either. To assess whether a new OS investment
would reap the benefits that are being sought after, this section will conduct,
firstly, an intangible and tangible costs/benefits analysis followed by a risk
analysis. The cost benefits analysis will be carried out by analyzing the Zara
business processes along the supply chain, between the shops and the
headquarters and among the shops. We will assume that a new OS would allow
for the installation of the latest software packages which can provide theoretical
inventory measures to the stores and distribution centers online. By means of an
integrated network, these data are then presumed to be accessible by the
production facilities, the HQ and all Zara stores.
If indeed the automated POS terminals would update the theoretical levels with
sales at the end of the day, then in principle orders could be made on a
continuous basis. The bottleneck in this case would then not be measurement of
inventory levels, but rather the frequency at which shipments arrive. Assuming
that orders would then occur on a daily basis, other tangible benefits would
include the optimisation of the inventory at the distribution centers. By using
modern e-supply management software, orders could be linked through an in-
house developed Enterprise Resource Planning (ERP) system that would link
orders made from stores to the rest of the supply chain. This would allow the
demand and supply to be matched even more closely though a more flexible
delivery system. This is not only because store managers would make orders
based on inventory levels at the distribution center, but also because HQ could
then more accurately align the supply to the stores’ demand. Production could be
adjusted on a daily basis by monitoring the orders that would come in, making
the production process even leaner. These adjustments would still need to be
made based on order quantities, since this would ensure store managers’
autonomy. In contrast to the current system, however, the software could
provide information on the Economic Order Quantity (EOQ) which dictates the
most optimal quantities that buyers should order to ensure that there is just
enough stock in the shops, to meet customer demands, whilst minimizing the
cost of inventory. The inventory level at which garments would have to be
reordered (also known as the ‘reorder point’) would provide store managers
with a structured approach towards inventory management, without
compromising autonomy. Further savings can be made if voice over IP software
would be installed to make calls between shops free. New OS could also support
wireless applications, which will be discussed in further detail later. In addition,
if the distribution centers would be connected to the network on the OS, store
managers could then place their orders after viewing whether the required
garments are available or not. The order could then be made to keep the
inventory level at the store updated, and a signal could get sent online to the
distribution centers and the production facilities. This would offer Zara stores
indirect benefits in the forms of extra sales due to more efficient customer
service, since more attention can be paid to the customer and more informed
orders could be made. Periodical checks would still need to be made to ensure
that the theoretical inventory levels match actual levels, since garments could go
missing or get stolen.
At the HQ, enterprise-wide software would allow designer to follow the sales of
test garments more closely, instead of relying on manual orders from store
managers. This would prevent any discrepancy to arise between orders and sales
as a result of manual calculations. Moreover, it would allow commercials to make
fairer allocations of items in case demand does exceeds supply as they could base
their decision on real and daily sales figures. Further benefits from an IT network
could be derived. For example, if all stores would have online access to other
stores, a particular store manager could direct a customer to another local Zara
store in case of a stock out. Conversely, the system could be set up in such a way
that shipments could be made from another local store, further reducing the
ordering period. To sum up, merging data into one system can enable the sharing
of sales information, ordering information and returns information leading to a
more precise measurement of the stocks and to a real time measurement.
Furthermore, regarding the current OS, an upgrade would prevent any hold up
from its terminal vendors. Indeed at the moment Zara has no insurance that its
supplier can provide terminals supporting DOS for a long term. Zara’s bargaining
power toward its supplier would increase.
Risks analysis
L.M. Apelgate et al. identified three important project dimensions which
determine project implementation risk: project size, technology experience and
project structure . Using these dimensions, the degree of risk associated with
changing from a DOS to a new OS was evaluated in the following manner.
Another factor impacting the degree of risk is structure of the project. The nature
of the project enables Zara to fully and clearly define the outputs of the project.
Notwithstanding the fact that project requires organizational changes and
modifications to store employee work habits (as a result of automating
information exchange and streamlining inventory control) the objectives of the
project are unambiguous, therefore enabling a focused approach of all the parties
involved. These are characteristics that typify a highly structured project.
Nonetheless, Zara should not discard dynamics in the environment since they
could upset the timing of the project or even determine the success of it. The
project involves technology which is relatively modern to Zara. Peculiarities of
each store (for instance, availability of instant IT support, learning abilities of
staff), political and cultural environment in the country of operating unit,
reliability of the vendor(s) for new POS terminals, etc., could make the project
vulnerable to delays and task alterations, and also challenging to manage.
Furthermore, although the IT investment relative to net income not substantial,
it is equivalent to Zara’s annual IT expenditure, making it a significant decision.
Given this and the fact that the project would have to implemented throughout
all the 531 stores with a relatively new technology for the company, the size of
the project is deemed to be large. However, realistic planning of the project, a
thorough understanding of store individualities and tight monitoring of project’s
progress, can eliminate potential frustrations and largely contribute to a
successful implementation.
To summarize the above, the dimensions have been plotted on a matrix to assess
the degree of implementation risk (please refer to figure 5). Zara’s project of
upgrading the POS terminal operating system with the characteristics described
above falls under a medium implementation risk category. For new system
testing and training purposes Zara should take advantage of its 1,500-square-
meter pilot store used to test store layout and design. This opportunity would
help to understand possible complications with cabling and could serve as an
excellent training facility for staff. More importantly, it would be wise for Zara to
have both the old and the new systems functioning simultaneously by carrying
out a staged roll out which will be discussed later. This would need to be done
until the store is ready to serve its customers uninterruptedly with the new
system to minimize the degree of risk. Finally, Zara must have a contingency plan
in place for unforeseen circumstance that may affect the success of the project,
including an exit plan if circumstances do not allow Zara to complete the project
as planned.
Let us assume that all of the additional costs (tangible and intangible) that have
been identified, other than the costs in figure 4, amount to an extra 20%. This
would increases our initial estimates of expenditure to €25.6 million (assuming
we choose Unix), which still constitutes only 0.64% of Zara’s revenues, on top of
the usual IT costs of 0.5%, whereas the industry average was 2% of annual
revenue . This is still well below the industry average. Although the investments
needed to implement this project are considerable in absolute terms, it does not
seem to be a make-or-break decision for Zara. The geographical extent of the
project, however, would make it a significant project. All stores in an area at the
last stage of the project would have to be upgraded quasi simultaneously, which
could prove to be a difficult task for management.
While there are various factors that contribute to the risk of the project these can
be mediated through careful management. Taking into consideration the
intangible costs discussed earlier, it can be concluded that this project has a
moderate risk to Zara. In terms of costs the risk is low, but in terms of project
coordination, the risks are slightly higher. There is no guarantee that if the
conversion run smoothly in one place, it will do so as well in another. The project
is a sizable one which affects all employees’ work. A thorough top down policy
would be required here, preceded by a pilot test in stores in different areas. The
costs of the change are reasonable and if a back-up plan is produced, the
identified risks could be contained. As the cost and benefit analysis suggests, the
project would safeguard Zara against its competitors and enable substantial
operational gains, through providing shop managers with valuable information.
In addition, the pending threat from the POS terminal supplier would be
mitigated. An upgrade of Zara’s OS is therefore recommended.
Question 4 - In-house Software Design and Single Supplier for POS Terminals
Historically, Zara has been able to keep software development in-house and
successfully meet requirements of the Zara Empire. Using POS terminals based
on an advanced operating system would open doors for more sophisticated
software needs and opportunities. This could make Zara reconsider maintaining
an in-house software development department. Alternatively, Zara could also
use standard applications or even outsource entirely. This topic takes us to the
discussion of transaction costs and the effect of IT on this theory. This can also
assist in guiding whether Zara should have only one POS terminal provider.
There are a number of reasons why Zara can consider outsourcing software
development, which conversely represents the disadvantages for in-house
application development. Firstly, outsourcing IT could provide opportunities for
cost reduction as it allows Zara to select the least expensive and most efficient
software vendors. Through a process known as reverse auction, Zara can post its
purchasing requirements and select suppliers based on the lowest bid offered.
The main argument here would be that if Zara could find an external vendor that
reduces it production and transaction cost, it would be the most favorable
option. This would mean that Zara would not have to worry about the in-house
staff with specific experience and skills for certain software pieces and could find
the latest software suitable for it operations. The result would be less
coordinating costs, since Zara would not have to monitor activities in-house as
this would be included in the service through a Service Level Agreement (SLA).
By using responsibility matrices the duties and rights can be mapped under
different circumstances. This would entail certain service level goals for the
supplier to adhere to and penalties in case of failure to meet these. If there were
a problem with the IT system, the supplier would therefore be legally obliged to
solve it immediately. Zara’s core competence, its speed to market, however,
would not be allowed to suffer under an outsourcing arrangement, and
considering Zara’s global presence, this raises the question as to whether
outsourcing forfeits flexibility. The issues of transaction and coordinating costs
are the main drivers in the trend of companies taking their IT activities
elsewhere. For Zara, this could entail less heavy investment in extensive projects
for keeping the IT system up-to-date, provided this is part of the contract or
switching costs are low enough. Moreover, outside suppliers might be more
specialized and be able to achieve greater economies of scale over in-house
production, provided the service is standardized. Recently, application software
providers even offer companies the possibility to store information remotely. If a
problem occurs with the connection however, this would entail a crash in the
entire supply. There are also security issues that cannot be overlooked. Even if a
company signs a confidentiality agreement, it does not ensure that sensitive
information will not be passed on to other parties. The risk of competitors
getting hold of this information and imitating essential processes such as Zara
swift inventory management is real and must be taken into consideration.
These advantages still do not form a strong case in involving a third party in
Zara’s operations if it wishes to be certain that the service will be of sufficient
caliber to meet its specific needs. Undoubtedly, cost reduction is one of the main
driving forces for outsourcing. If pursuing cost reduction as the outsourcing
objective, it would be more beneficial to consider offshoring (typically to China
or India), as this offers reduced labour costs. However, this option may have
serious implications due to possible cultural differences and political instability
in the outsourced country. Language barriers and communication problems may
further enhance complications of this decision. One must bear in mind that if
Zara is to outsource its software, the desired specifications also need to be
contractible. This is a major issue in outsourcing, referred to as bounded
rationality. Incorporating and agreeing upon factors such as quality of IT service,
innovation, information sharing, supplier responsiveness (accommodating
buyer’s non-contractual requests), and flexibility is very difficult to stipulate in a
contract in advance. Furthermore, including all the possible future states of
nature that could have an impact on the SLA is naturally infeasible. With further
reference to transaction cost theory, outsourcing only makes sense if complexity
of a product description and asset specificity are low. In Zara’s case, the asset
specificity is relatively high. This is because its success is partially built upon a
robust supply chain and flexibility, so time specificity is an issue which hinders
outsourcing. In addition, as a result of Zara’s widespread network, the
complexity of the IT solution would be relatively high. If something goes wrong
in any of the stores, an outside IT supplier might not be responsive enough to
meet immediate needs in the same way in-house software designers would.
Figure 6 offers a graphical representation of the situation. Although EMH
suggests that IT will generally lead to a shift towards markets for economic
transactions, this is not believed to be sufficient to offset the high specificity and
complexity of the Zara’s IT requirements. Another pitfall can be in the tender
through reverse auction. Although the potential suppliers will be tempted to
offer the lowest price, this might not bode well for the promised services. Having
a supplier for the lowest price might not guarantee the services that Zara
requires. Moreover, suppliers can make offers without being aware of the full
scope of the project.
The basic premise for EMH is that by and large, IT would lead to lower
transaction costs that would in turn lead to greater reliance on arm’s length
relationships with many suppliers. In contrast, MMH coincides with EMH in
terms of outsourcing but predicts a move towards long-term relationships with a
smaller set of suppliers. In spite of the risks related to the dependency, having a
single vendor might lead to long-term relationships which will allow Zara to
enjoy economies of scale as a result of investments in IT required to coordinate
supply relationships. It would also allow Zara to economize on search costs
which would be a result of having several suppliers. When a terminal breaks
down it is probably better to have a solid relationship with one supplier to
ensure swift response time to minimize the downtime. Chances are that this will
be more realistic with fewer suppliers, as it would provide the vendor with
greater incentive to be of service than with multiple suppliers. The current POS
supplier is still servicing Zara, and although there were reluctant to ensure
contractually service in the future, it served as a strong motivation to consider
the benefit of upgrading its system. If there would have been several suppliers in
the current story, it could well have been an excuse to only partially upgrade the
terminals or negotiate with other providers to expand the outdated terminals. In
short, the benefits from diversification in this context does not necessarily lead
to greater efficiency and might lead to complacency. Considering the benefits of a
new OS identified in this paper, the hold up position is therefore not necessarily
negative. Again, there are also security risks that play a role and when there is a
lack of incentive there will also be a lack of mutual trust which in this situation is
not desirable. Zara needs fast after sales services with a POS supplier that it can
rely on. If Zara would have to opt between a single supplier or several, the
former would be probably more suitable.
Being a part of the key instrument in the value chain, it considered best for Zara
to retain software development in-house. The IT department of Zara has a
unique culture of a relatively small and highly motivated group of people (only 1
person left the department over the last 10 years!) based in La Coruñ a, who are
responsible for the entire Inditex group of companies. Empowerment of
employees adopted in Zara gives a sense of ownership to the software
developers with regards to the produced applications, which increases
productivity and job satisfaction. Software developers are involved in a creative
process as opposed to the IT staff needed to only monitor outsourced activities.
The benefits from outsourcing may not be sufficient to cover the costs that would
be incurred as a result of the complexity of the product and asset specificity,
despite the coordination costs that are involved in internalizing IT suppliers.
Zara’s core competence is at stake, and it is believed that by retaining a internal
designer would be the best way to preserve it, provided the supplier can meet
Zara’s global needs. Similarly for its POS terminals, although Zara has slipped
into to a hold up position it could prevent this in future by maintaining a more
stringent company IT program. Although the chance of a hold up exists, the
downside to having multiple suppliers could potentially threaten its speed.
Having a single supplier for the POS terminals will lead to an accumulated
knowledge in customization of equipment and services, and result in closer
match to Zara’s preferences. Zara needs to ensure a continuous link between
overall corporate strategy and the IT strategy. For that reason it is deemed
important that Zara retain bilateral agreements with its POS suppliers.
1-Develop scenarios: The first step would be to consider the potential scenarios
and outcomes of the IT project for Zara, that is, the upside and downside
possibilities and their probability of occurrence in order. This preliminary
review, if it has not been done previously, would offer significant insight into the
company’s strategies, even if real option analysis has not yet been implemented.
2-Search for options: After developing the scenarios, the project should be
examined to see which type of option is most appropriate. There are numerous
types of options. Some allow for a project to expand (known as expand options)
others allow for the projects to be suspended until the situation is favorable
(known as defer option). Fundamentally, they all involve a choice which is
contingent upon the future state of nature. This provides the investing firm with
a flexibility value. A very interesting type of option for Zara’s purposes is the
stage option. It is widely used for IT projects and allows for the project to be
divided up into several stages, where after each stage the investor has the option
to abandon at virtually any predefined decision point of the project. Most
investments are not made frivolously and do not entail a single up-front outlay,
but instead are staged and sequential. This would probably apply as well to the
Zara’s global IT project (+€21m). The reason why it is especially appealing for
the IT implementation of Zara is because it will prevent Zara from having to
launch a full-fledged project across the globe without being able to test the
waters first. Figure 7 gives an example of how to geographically stage the project
in Europe. A possible way of staging the project would be by starting with a pilot
test at the HQ and production facilities for a predetermined time period (Please
see figure 7, Stage 1). If this goes according to plan, the next step would be to
choose a district in Spain and select five stores to act as a platform for the new
OS and in-house developed software for another time period (stage 2).
Interaction with the production facilities and distribution centers could also be
incorporated at this stage. Next would be a nation-wide roll out of the IT project
(stage 3) followed by a European implementation (stage 4). The last stage could
be the global implementation. The way in which this is done can be left to the
discretion of management, the purpose is merely to illustrate successful
execution of the stage option. There is obviously some hesitation within the
company related to the leveraging of ‘fancy’ technology, so the key issue, is
therefore to choose the stages and time periods in such a way that any risks are
mitigated. A more conservative approach might be to have pilot stores in every
country to account for the different cultures and learning curves. The next step in
our analysis is determining what information is necessary to value the option
premium. Eventually the decision options are either to go for the next stage in
the project or to maintain course and stay with the old OS. This depends on the
outcome of the option valuation of that particular phase and incorporates the
investment required. A positive value indicates the premium therefore making it
worthwhile to proceed. The valuation procedure for the stage option is explained
below. Conversely, if the option value is negative, this might be an indication that
an IT upgrade might not offer the enough added value which could suggest that
Zara should abandon the project and stick to its current system.