Read a sample: 1. The Technology Decision Is a Leadership Decision
The proposal arrives wrapped in a familiar promise: a new tool will make work easier to see, easier to manage, and easier to improve. Its dashboard is polished. The demonstration answers several questions that have frustrated managers for months. The price seems manageable, and the vendor says the software can be running quickly.
Then someone asks what the tool will record about employees.
The room becomes quieter. The demonstration showed a chart of team activity, but it did not explain whether a manager could inspect an individual’s behavior, how long the underlying records would be kept, or what an employee could do if the chart created a misleading impression. Those details may be available, but no one at the meeting has asked for them yet.
That pause is not a distraction from the technology decision. It is the technology decision.
Choosing workplace software is rarely just a matter of comparing features and prices. A tool can change who has information, how work is judged, which employees can participate comfortably, and how easily a mistake can be corrected. Even a purchase intended to solve a narrow operational problem can affect relationships across a workplace.
Leaders do not need to become software engineers to make these decisions well. They do need to recognize the choices hidden inside a proposal and take responsibility for the conditions under which a tool is used.
Consider a hypothetical company, Northstar Services, that supports customers through phone calls, email, and internal casework. Its managers have noticed that some customer requests take longer to resolve than they would like. Employees say they often have to search several systems for information, wait for approvals, and interrupt one another to find the right person to help.
An operations director proposes a new workplace analytics tool. According to the vendor, it can bring information from several systems into one dashboard. Managers could see case volumes, response times, and patterns in how work moves between teams. The vendor also offers an individual activity view that displays when employees use certain applications and how long particular tasks appear to take.
The proposal is appealing for understandable reasons. Customers are waiting. Managers cannot easily see where cases stall. Employees are frustrated by repeated searches and unclear handoffs. Better information might help Northstar improve its service and remove obstacles from employees’ work.
But the individual activity view introduces questions the initial proposal has not resolved. Does Northstar need that level of detail to identify bottlenecks? Would it show meaningful work, or mostly the work that happens inside tracked applications? Could the information be used in performance conversations? Would employees know what was visible and have a way to challenge an inaccurate interpretation?
Northstar’s decision is not simply whether the dashboard is impressive. It is whether a particular use of the tool is a proportionate and workable response to a defined problem.
This scenario will accompany us throughout the book. At this stage, there is no need to decide whether Northstar should buy the software. The useful first step is to notice how many decisions sit inside what initially looks like one purchase.
A technology proposal often arrives as a package: a product, a price, a demonstration, and a suggested rollout. Leaders may feel that the available choices are to approve the package or reject it. In practice, the decision has more parts.
Northstar’s leaders could choose to collect team-level case information while declining the individual activity view. They could ask the vendor to demonstrate whether certain functions can be disabled. They could decide that a limited test is appropriate only after employees have been consulted and key questions answered. They could also conclude that process changes deserve a trial before any new software is introduced.
Each option reflects decisions about purpose, boundaries, and responsibility:
- Purpose: What problem is the organization trying to solve, and for whom?
- Information: What does the tool need to collect or display for that purpose?
- Access: Who can use the tool, see its outputs, and seek help?
- Authority: Who may act on an output, and who can review or correct it?
- Duration: When will the organization revisit the decision, and what might cause it to stop?
These questions apply whether a workplace is considering scheduling software, a hiring platform, a communication tool, automated summaries, location tracking, or a system that helps managers allocate work. The details will differ, as will the stakes. A shared calendar and a tool used to assess employee performance do not call for identical reviews. Both, however, benefit from a leader being clear about what is being introduced and why.
A vendor can describe its product. A technical specialist can explain configurations and limitations. Human resources, legal advisers, and security professionals can contribute expertise. Employees can explain how work actually happens. The leader’s role is to bring those perspectives into a decision and make sure someone remains accountable for its effects.
Delegating investigation is sensible. Delegating responsibility to the software, or assuming that a vendor’s default settings settle the matter, is not.
An attractive feature answers the question, “What can this product do?” A business need answers a different question: “What are we trying to improve?”
The distinction matters because a feature can be useful without being necessary for the problem at hand. Northstar’s individual activity view might provide detailed information about application use. That does not establish that individual application use…