Unit 4 Technology Strategy and Competitiveness
Unit 4 Technology Strategy and Competitiveness
UNIT 4
TECHNOLOGY STRATEGY AND COMPETITIVENESS
4.1. Introduction:
• Strategy is a plan or framework that is designed to achieve the organizational goal.
• Technology Strategy is the overall plan or framework designed by including
company's principles, tactics etc to achieve the company’s goal.
• Strategy Management is the continuous planning, monitoring, analysis and
assessment of all that is necessary for an organization to meet its goals and objectives.
• The strategic management process involves analyzing cross-functional business
decisions prior to implementing them. Strategic management typically involves:
✓ Analyzing internal and external strengths and weaknesses.
✓ Formulating action plans.
✓ Executing action plans
• Objectives: The objectives define the success metrics and clarify the details of vision
statement. The objectives use the vision of the accessible technology.
• Expenses and budget: This involve the clarification that is done in regard to the
expenses, and describes the funding resources. This explains which expenses should
become a part of overall technology purchase, and which should come under a separate
budget. Some organisations include the assistive technology product costs in the main
centralised accommodation budget, and some companies deduct these expenses from
the individual technology budgets of each department. It is important for us to clarify
the budget decisions and see that the funds are allocated appropriately
• Ownership: The ownership defines the responsibilities of the team members in the
project. The ownership also plans the execution of the project. There should be one
committee to see whether the execution of the plan is moving correctly or not
• The process of translating an idea or invention into a good or service that creates value
or for which customers will pay is knows as Innovation.
• ‘innovation management’ is defined as the systematic processes that help the
organisations in developing new and improved products, services and business
processes.
• Cost Focus Strategy: This strategy is quite a resemblance to the cost leadership
strategy; however, a major difference is that the cost focus strategy businesses target a
particular segment within the market and that segment is offered the lowest price of
the product or service. This type of strategy is very useful to satisfy your consumer and
increase brand awareness. For example, beverage companies manufacturing mineral
water can target market segment like Dubai, where people need and use only mineral
water for drinking, can be sold at a lower than competitors.
• Go-Live Considerations: Finally, it is essential that the “go live” day causes as tiny
disturbance to the daily business, since it is practically possible. The various issues
arising at this point of time will negatively affect the organisation’s status, sometimes
irreversibly, with all stakeholders.
✓ Be cautious: If the new chosen technology provides revenue to your business, then it
is necessary to be careful while making any major modifications in the new technology.
Being cautious does not merely mean that you should avoid the advancing technology.
It conveys to be more careful in understanding the consequences and secondary
applications which may perhaps be impacted as a result of a very small change. If we
consider examples, of some companies that had apparently made changes to billing,
failed to produce invoices or statements to the clients. The consequence formed
economic poverty for the billing company, and for the displeased customers, who
abruptly received several months’ worth of amass billing once the accounting system
problem was resolved. In addition to the impact on cash flow, the relationships with the
customers become weak. Henceforth, you should be aggressive to increase the
competitive chances to grow the profit and performance of your business. At the same
time, you must be careful even while implementing changes that may affect your core
business contributions, customers, or billing.
✓ Be quick: It is important for you to be quick enough to implement the small changes to
your chosen technology and to supervise their impact. There should not be any delay,
when it comes to performance improvement, internal proposal for simplifying routines
or improving customer performance. We must follow a set of routines, to design small
changes, test changes and schedule to bring consistent enhancements. It is pretty often;
the minor improvements encompass the major impact to business performance.
✓ Be slow: If major changes affect your business, it is vital to make the implementation
changes slowly. Normally, the centre design and functions of the business are well-
organised and updated. The processes that are more frequently in use are likely to get
the majority attention and seem to be highly evolved. Basically, these processes are
given the first priority, when it comes to implementing a transfer in technology. On the
other side, you must avoid focusing on common ground, also conserve the primary
processes until the changes have been tested on some of the more difficult and less used
utilities. There will be remarkable information to be achieved with the experience and
less effect on business by concentrating on most composite and least used functions. O
✓ Be safe: During the implementation of a new technology, the better time to address the
potential security needs is at the time of design and development. It is better to employ
a security expert who will take care of the privacy of the organisation. If you have
customers, credit cards, customer accounts, customer information, intellectual
belongings, monetary information, health information, or employee information stored
automatically, available on a network, or printed in files, then it is vital to consider
safety. Also, if you are planning to undergo a technology change, it is the right time to
reassess the associated documents by means of a security or privacy specialist.
Step 2: Analysis
• By the end of the discovery stage, you should be armed with information about where
you are now and where you want to go. Ideally, you’ll have the beginnings of
requirements to get there.
• Next, you need to analyze the precise functionality that you have internally and how
it’s currently being applied.
• Since you have a good understanding of the problem, the goal, and the environment
and systems, a good place to start is to look at what your existing tech stack can do.
• You need to look at how the technology is being applied at a granular level.
Step 4: Document
• The final step is to put all your work down on paper in a well-documents plan.
Your final document should include:
• A high-level overview,
• A crisp explanation of what you are solving and what you are asking for
• All the details of the implementation and deployment
• Details on project timelines and ownership.