Intro to Business › Section M · Technology and information › Topic M.4
Technology management and planning
Buying technology is easy; getting value from it is not. Technology management and planning tie every IT investment to a business goal, decide which projects deserve money first, and make sure an organisation's knowledge, not just its data, is put to work.
Why IT spending disappoints
Firms spend heavily on information technology, yet many senior managers complain that they do not get enough in return. The common complaints are familiar: spending is too high for the results; projects are not linked to business strategy; the firm buys the newest technology for its own sake; and IT specialists and the people who use the systems do not understand each other. None of these is a technical failure. Each is a management failure, which is why technology must be planned and governed like any other major investment, with clear goals, owners and measures of success.
Managing IT across the firm
Running a firm's IT is hard because it spans many locations, devices, applications and outside cloud services, all under time and budget limits. Growing firms often end up with a patchwork of separate systems that duplicate effort and do not share data. Ageing legacy systems may be costly to maintain but risky to replace. The aim is one plan for the whole firm, weighing business judgement, technical expertise and the money available. Good plans also get more from what the firm already owns, by retiring duplicate tools, consolidating licences and training people to use existing systems fully.
IT governance
IT governance is the set of decision rights and processes that decides which technology projects go ahead, who pays and who is accountable. Many firms use a steering committee of senior executives, IT leaders and business-unit managers to review proposals together, so that projects reflect the firm's priorities rather than whichever department pushes hardest. Governance also sets standards, such as approved software and security rules, and reviews projects after they finish to see whether the promised benefits arrived. Without it, departments may buy their own tools without IT's knowledge, which creates security risks and duplicate costs.
From information to knowledge management
Information management collects, processes and condenses information. Knowledge management (KM) is the harder task of capturing, organising and spreading what an organisation's people collectively know, so that work gets faster, ideas multiply and the firm stays ahead of rivals. Some firms appoint a chief knowledge officer to lead it. Knowledge comes in two forms. Explicit knowledge can be written down, such as procedures and reports. Tacit knowledge lives in people's heads as experience and judgement, such as how a veteran engineer diagnoses a fault, and is far harder to capture. When experienced staff leave, tacit knowledge can walk out with them.
Making knowledge management work
KM is a business practice that uses technology, not a software purchase. A firm that installs a large knowledge database and expects people to fill it usually fails. Successful programmes start with specific, costly problems, such as researchers spending hours searching separate databases, and solve those first. They build a culture that rewards sharing, through recognition, time and incentives. Useful tools include searchable document stores, expert directories that show who knows what, communities of practice where people in similar roles swap lessons, and mentoring to pass on tacit knowledge. Newer AI search tools can help people find answers across many documents at once.
The technology planning process
A good technology plan gives employees the tools they need to work efficiently. It follows a sequence. First, a needs assessment asks what the company's objectives are, what problems it must solve and how technology could help. Second, projects are ranked by priority, short and long term. Third, specific technologies are chosen, checking whether they fit the infrastructure and integrate with existing systems. Fourth, the firm decides whether it has the skills in house or needs outside specialists. Fifth, the system is developed or bought, implemented with training, and evaluated against the benefits promised at the start.
Fix the process first
Technology projects succeed when they change how work is done, not just the tools used to do it. Installing a new system on top of an inefficient process simply makes the inefficiency faster: if approving an invoice needs five signatures, an electronic form with five signatures is barely an improvement. Planners should first map the current process, remove unnecessary steps and only then choose technology to support the new design. People matter as much as process. Users should be involved early, trained well and given reasons to change, because a system nobody uses delivers no benefits.
Worked example: ranking projects
A firm can fund only one project this year. It scores each from 1 to 10 on strategic fit (weight 0.40), expected benefit (0.35) and low risk (0.25). 1. CRM upgrade, scores 8, 7, 6: \(0.40 \times 8 + 0.35 \times 7 + 0.25 \times 6 = 7.15\). 2. Warehouse scanners, scores 6, 9, 8: \(2.40 + 3.15 + 2.00 = 7.55\). 3. New intranet, scores 5, 5, 9: \(2.00 + 1.75 + 2.25 = 6.00\). 4. The scanners rank first, although the CRM upgrade fits strategy best. Check: the weights sum to 1, so each score stays on the 1 to 10 scale; changing the weights could change the ranking, so they must be agreed before scoring.
Worked example: payback and return
The warehouse scanners cost 120,000 dollars to install. They are expected to save 45,000 dollars a year in labour and errors, and cost 5,000 dollars a year to run. 1. Net annual benefit: \(45{,}000 - 5{,}000 = 40{,}000\) dollars. 2. Payback period: \(120{,}000 \div 40{,}000 = 3\) years. 3. Over a five-year life, total net benefit is \(5 \times 40{,}000 = 200{,}000\) dollars. 4. Simple return: \((200{,}000 - 120{,}000) \div 120{,}000 \approx 66.7\%\) over five years. Check: these measures ignore the timing of money, which later finance topics treat more carefully, and the savings are only estimates.
Build, buy or subscribe
For each need, a firm can build its own software, buy a packaged product, or subscribe to a cloud service. Building offers an exact fit and can create a competitive edge, but it is slow, costly and needs skilled staff to maintain. Buying is quicker and cheaper but may force the firm to adapt its processes. Subscribing spreads costs over time and shifts maintenance to the provider, but creates ongoing fees and dependence on the vendor. The fair comparison is total cost of ownership: purchase or fees, hardware, support, training, staff time and eventually replacement, over the system's whole life.
Common mistakes to avoid
First, starting with a technology rather than a business problem. Second, automating a poor process unchanged, which makes it faster but no better. Third, treating knowledge management as buying a database, when it depends on culture and incentives. Fourth, comparing options on purchase price instead of total cost of ownership. Fifth, ranking projects with weights chosen after the scores, which lets favourites win. Sixth, forgetting to check after a project ends whether the promised benefits actually arrived.
Key takeaways
IT disappoints when it is not tied to strategy, so technology needs planning and governance like any major investment. A company-wide plan integrates systems and gets more from existing ones. Knowledge management shares collective knowledge, explicit and tacit, and works through culture and specific problems rather than software alone. Planning runs from needs assessment to ranking, choosing, implementing and evaluating. Fix the process before automating it. Weighted scores rank projects; payback = cost ÷ net annual benefit. Build, buy or subscribe should be compared on total cost of ownership.
Flashcards
Flashcard
Company-wide plan tying IT investment to business goals
Test your understanding
Question 1 of 5
A system costs 60,000 dollars, saves 20,000 dollars a year and costs 5,000 dollars a year to run. What is its payback period?
Question 2 of 5
A project scores 6, 8 and 10 on criteria weighted 0.5, 0.3 and 0.2. What is its weighted score?
Question 3 of 5
How does knowledge management differ from information management?
Question 4 of 5
What should come first in a technology planning process?
Question 5 of 5
An invoice needs five signatures and takes two weeks. What is the best approach to a new system?
