The future of work in technology can be understood through three connected dimensions:
1. Work: What must be accomplished, which tasks are involved, and how people, software, automation, and AI agents divide those tasks
2. Workforce: Who performs the work, which skills are required, and how employees, external specialists, vendors, and intelligent systems are combined
3. Workplace: Where and how collaboration, decision-making, learning, and delivery happen
Deloitte’s original framework argues that organizations should define future work and desired outcomes before redesigning their workforce or physical workplace. It describes a shift from technology capabilities and projects toward products, customer outcomes, and measurable business value. That principle has become even more important as generative and agentic AI enter technology organizations.
AI can now assist with or perform portions of:
- Software development
- Testing
- Documentation
- Research
- Infrastructure operations
- Cybersecurity analysis
- Customer support
- Data preparation
- Product discovery
- Incident investigation
This does not mean technology professionals simply disappear. It changes where human contribution creates the most value.
Human workers are likely to concentrate more heavily on:
- Defining the right problems
- Making architectural decisions
- Exercising judgment
- Understanding customers
- Managing risk
- Designing systems
- Integrating technologies
- Verifying AI outputs
- Coordinating teams and agents
- Connecting technology to business strategy
McKinsey’s 2026 research argues that AI is forcing companies to reconsider technology hiring, internal capability development, and vendor strategy together. As agents perform more routine execution, demand may shift toward senior engineers, architects, designers, product leaders, and professionals who can coordinate human and machine work. At the same time, the technology labor market remains substantial. The US Bureau of Labor Statistics projects that employment in computer and information technology occupations will grow much faster than the average for all occupations from 2024 through 2034, with approximately 317,700 openings annually from growth and worker replacement. The future is therefore not accurately described as either unlimited technology hiring or total AI replacement. It is a reallocation of tasks, skills, accountability, and organizational design.
The most important actions for technology leaders are:
- Begin with business and customer outcomes
- Analyze jobs at the task level
- Decide what humans, automation, and AI agents should each perform
- Organize around persistent products and services rather than temporary projects
- Build cross-functional business-technology teams
- Replace rigid job descriptions with evolving skills and responsibility profiles
- Develop continuous learning inside daily work
- Use internal and external talent intentionally
- Redesign junior career pathways
- Measure value, quality, resilience, and customer impact rather than activity alone
- Build a workplace that supports distributed human and AI collaboration
- Establish strong governance for security, accountability, data, and AI decisions
The central strategic question is no longer:
How should the IT department operate?
It is:
How should the entire organization combine people, technology, partners, and intelligent agents to create business value?
1. Technology Is No Longer Merely Supporting the Business
For decades, technology departments were commonly viewed as internal service organizations.
Their responsibilities included:
- Maintaining systems
- Managing infrastructure
- Installing applications
- Supporting employees
- Protecting networks
- Delivering technology projects
Business leaders decided what the company wanted to accomplish. The IT department was asked to provide the systems required to support those decisions. That division is becoming increasingly unrealistic. In many modern organizations, technology does not merely enable the product. Technology is part of the product. A financial company may compete through digital payments, automated underwriting, fraud detection, mobile applications, and data-driven personalization. A retailer may compete through e-commerce, logistics software, recommendation systems, inventory intelligence, and digital customer experience. A manufacturer may depend on robotics, connected equipment, predictive maintenance, digital twins, and automated quality control.
Technology choices therefore influence:
- Revenue
- Customer loyalty
- Product differentiation
- Operating cost
- Business resilience
- Market speed
- Competitive advantage
Deloitte’s framework describes a transition from technology as a trusted operator toward technology as a business cocreator. It also argues that technology organizations are moving away from project-centered delivery and toward product and outcome-centered models. The distinction is important. A project has a defined beginning and end. A product or service continues evolving in response to customer behavior, business needs, technology changes, and competitive pressure.
2. The Three Dimensions of the Future of Technology Work
Technology workforce transformation frequently begins in the wrong place. A company sees a shortage of AI talent and starts recruiting. It adopts hybrid work and redesigns offices. It purchases an AI coding tool and announces a productivity target. These actions may be useful, but they remain disconnected if the organization has not defined the work it is trying to accomplish.
Deloitte divides the future of work into three interrelated dimensions:
- Work
- Workforce
- Workplace
It recommends beginning with work outcomes before deciding who performs the work or where it should happen.
Work asks:
- What outcome must be produced?
- Which tasks create that outcome?
- Which activities add value?
- Which tasks should be automated?
- Where is human judgment required?
Workforce asks:
- Which skills are necessary?
- Which roles will own decisions?
- Which capabilities should remain internal?
- Where should external talent be used?
- How should humans and AI agents collaborate?
Workplace asks:
- Which activities require physical presence?
- Which work can happen remotely?
- How will distributed teams collaborate?
- What tools and rituals support trust?
- How will people learn from one another?
These three dimensions must be designed together.
3. Start With Outcomes Rather Than Existing Jobs
Organizations frequently treat current jobs as permanent building blocks. They ask how AI can make the existing software engineer, project manager, security analyst, or support specialist more productive.
A better question is:
What outcome is this role intended to produce, and what is the best future combination of people and technology for producing it? For example, consider software quality. The desired outcome is not to employ a certain number of testers. The outcome is reliable, secure software that satisfies user requirements.
The work may include:
- Requirements analysis
- Automated testing
- Manual exploratory testing
- Security testing
- Performance testing
- Defect investigation
- User feedback
- Release decisions
AI may generate test cases and identify likely defects. Automation may run repetitive tests. Human specialists may focus on unusual behavior, security, usability, risk, and release judgment. The job changes because the work is decomposed.
4. From Projects to Products and Persistent Value Streams
Traditional IT organizations are often structured around projects. A business department requests a system. A project receives funding. A temporary team implements it. The project is completed. The system is transferred to another group for maintenance.
This creates several problems:
- The implementation team may disappear after launch.
- Long-term product ownership may be unclear.
- Success may be measured by budget and schedule rather than user value.
- Maintenance and improvement become separated.
- Teams repeatedly form and dissolve.
A product model organizes people around a continuing customer, employee, platform, or business outcome.
Examples include:
- Customer onboarding
- Digital payments
- Employee collaboration
- Data platform
- Developer platform
- Fraud prevention
- Supply-chain visibility
A persistent team owns:
- Product direction
- Technology
- User experience
- Reliability
- Security
- Improvement
- Business results
Deloitte argues that a product mindset views technology work as solving a continuing business problem rather than merely delivering application functionality.
5. AI Is Changing Tasks Faster Than Entire Occupations
Discussions about AI frequently focus on whether a whole job will disappear. That framing is often too broad. Most jobs are collections of tasks.
A software engineer may:
- Clarify requirements
- Design architecture
- Write code
- Review code
- Test systems
- Investigate incidents
- Meet customers
- Mentor colleagues
- Document decisions
AI may perform some of these tasks well, assist with others, and remain unsuitable for several. A security analyst may use AI to summarize alerts while retaining responsibility for assessing business risk. A product manager may use AI to analyze feedback but still decide which customer problems deserve investment. A cloud engineer may automate infrastructure creation while retaining responsibility for resilience, security, and architecture. The future of technology work should therefore be designed at the task level.
6. A Framework for Dividing Work Among Humans and AI
Every technology activity can be evaluated across four possible categories.
6.1 Human-led work
Humans should remain directly responsible when the activity requires:
- Ethical judgment
- Strategic choice
- Accountability
- Empathy
- Ambiguous problem solving
- Political awareness
- High-stakes risk decisions
- Customer trust
Examples include:
- Approving a major architecture
- Accepting cybersecurity risk
- Prioritizing product investments
- Managing employees
- Communicating during a crisis
6.2 AI-assisted work
AI can increase speed or quality while a human remains responsible.
Examples include:
- Code generation
- Documentation drafting
- Incident summarization
- Data analysis
- Research
- Design exploration
- Test generation
The person reviews, corrects, and accepts the result.
6.3 AI-supervised work
An agent may perform a larger sequence of tasks while a person monitors performance and handles exceptions.
Examples include:
- Routine infrastructure remediation
- Support-ticket resolution
- Software maintenance
- Data-quality correction
- Automated reporting
6.4 Fully automated work
Automation is appropriate when:
- Rules are clear
- Risk is limited
- Outputs are measurable
- Exceptions are understood
- Reversal is possible
The objective is not to maximize automation. It is to choose the safest and most valuable division of responsibility.
7. The Rise of the Human-Agent Technology Team
Technology teams are beginning to include AI agents that can:
- Generate code
- Review pull requests
- Run tests
- Investigate incidents
- Update documentation
- Search repositories
- Analyze requirements
- Monitor infrastructure
This creates a new management challenge.
Leaders must determine:
- Which agents are approved
- What systems they may access
- Which actions require human approval
- How outputs are verified
- Who is accountable for errors
- How agent activity is logged
- How sensitive data is protected
McKinsey argues that hiring, internal capability building, and vendor strategy can no longer be treated as separate decisions in an agentic environment. Together, they determine where human judgment remains, which capabilities the organization owns, and whether AI value is captured internally or absorbed by providers.
8. Technology Roles Will Become Broader and More Business-Oriented
Technical depth will remain essential.
However, many technology professionals will also need greater understanding of:
- Customers
- Revenue
- Operations
- Finance
- Regulation
- Risk
- Product strategy
Deloitte’s analysis emphasizes that enduring human capabilities such as business understanding, collaboration, empathy, creativity, learning, and comfort with uncertainty will complement technical expertise. This does not mean that every engineer becomes a generalist. It means technical decisions are increasingly evaluated according to business outcomes. An architect should understand how design affects cost, resilience, speed, and customer experience. A data scientist should understand how a model affects operational decisions. A security professional should explain risk in language executives can use.
9. New and Expanding Technology Roles
AI and automation may reduce some tasks while increasing demand for others.
Growing or expanding role categories may include:
- AI product manager
- AI systems architect
- Agent operations engineer
- AI security specialist
- Model-risk manager
- Responsible AI leader
- Platform engineer
- Site reliability engineer
- FinOps specialist
- Data-governance professional
- Developer-experience leader
- Automation architect
- Human-AI interaction designer
- Agent workflow designer
The US labor outlook remains strong across computer and information technology occupations overall, even though growth will vary substantially among individual roles.
10. Some Traditional Roles Will Change Significantly
Software developers
Developers may spend less time producing routine code and more time:
- Designing systems
- Reviewing AI-generated code
- Integrating components
- Securing applications
- Understanding users
- Managing technical quality
Quality-assurance professionals
Testing may shift from repetitive execution toward:
- Test strategy
- Exploratory testing
- AI-output evaluation
- Security
- Reliability
- User behavior
Infrastructure professionals
Manual server administration may decline while demand grows for:
- Cloud architecture
- Platform engineering
- Automation
- Observability
- Reliability
- Cost optimization
Support professionals Routine questions may be resolved automatically.
Human support specialists may focus on:
- Complex cases
- Customer emotions
- Escalation
- Product feedback
- Knowledge improvement
11. The Junior Talent Pipeline Requires Redesign
AI can perform many tasks traditionally assigned to early-career technology workers.
These tasks included:
- Simple coding
- Basic testing
- Documentation
- Research
- Ticket resolution
- Data preparation
Removing this work may increase short-term productivity. It can also damage the future talent pipeline. Senior professionals became senior by practicing on lower-risk work. If AI performs all junior tasks, companies must create alternative development pathways.
Possible approaches include:
- Apprenticeships
- Pairing junior employees with senior staff and AI
- Rotations
- Structured code review
- Simulated incidents
- Customer exposure
- Architecture learning
- Supervised agent management
McKinsey’s 2026 technology-workforce analysis suggests that the business case for hiring large numbers of junior developers may weaken as agents absorb more basic execution work. That makes deliberate career development more important, not less.
12. Static Job Descriptions Will Become Less Useful
Traditional job descriptions assume stable responsibilities. Technology roles change too quickly for that model. Deloitte proposes replacing fixed job descriptions with more flexible “job canvases” that describe changing skills, broader responsibilities, work outcomes, and how automation affects the role.
A modern role profile might include:
- Core outcomes
- Current responsibilities
- Skills increasing in importance
- Skills decreasing in importance
- AI tools used
- Decisions reserved for humans
- Collaboration relationships
- Expected development path
This allows roles to evolve without rewriting the organization every few months.
13. Continuous Learning Must Move Into Daily Work
Traditional training often separates learning from work. Employees attend courses and later return to jobs that do not use the new skills.
Future learning should be:
- Continuous
- Practical
- Role-specific
- Embedded in projects
- Supported by peers
- Connected to advancement
Useful methods include:
- Apprenticeships
- Internal projects
- Communities of practice
- Pair programming
- Mentoring
- Rotations
- AI-assisted coaching
- Technical demonstrations
- Post-incident learning
Deloitte argues that technology professionals need real-time learning and rapid knowledge transfer because skills evolve too quickly for occasional training cycles.
14. The Workforce Will Extend Beyond Employees
Technology work can be performed by:
- Permanent employees
- Contractors
- Freelancers
- Consulting firms
- Managed-service providers
- Open-source communities
- Universities
- Strategic partners
- AI agents
Deloitte refers to this as an open talent continuum and argues that organizations need a more integrated approach to accessing and managing internal and external talent. The correct model depends on the capability.
Keep strong internal ownership when the work involves:
- Core product differentiation
- Enterprise architecture
- Cybersecurity decisions
- Strategic data
- Customer trust
- Technology governance
Use external specialists when the work is:
- Temporary
- Highly specialized
- Project-based
- Rapidly changing
- Difficult to staff permanently
Use managed services when the capability is:
- Continuing
- Standardizable
- Operational
- Better delivered at provider scale
15. Vendor Strategy Is Becoming Workforce Strategy
Technology providers increasingly supply more than software.
They may provide:
- AI agents
- Embedded experts
- Managed operations
- Data services
- Automated workflows
- Outcome-based services
This means vendor selection determines where capability resides. If a company outsources too much, it may lose the skills needed to evaluate architecture, cost, risk, and quality. If it insists on building everything internally, it may move too slowly. McKinsey argues that organizations should restructure vendor relationships around outcomes and interoperability while avoiding excessive lock-in and preserving internal capability.
16. Technology Teams Must Become Cross-Functional
Business and technology can no longer work effectively as separate departments connected by project requests.
A cross-functional product team may include:
- Product manager
- Software engineer
- Designer
- Data analyst
- Security specialist
- Operations representative
- Customer expert
- AI agent
The team shares responsibility for an outcome.
Examples include:
- Increasing checkout completion
- Reducing fraud
- Improving delivery accuracy
- Accelerating employee onboarding
- Reducing application downtime
Deloitte argues that the boundaries between business and technology work will continue to blur and that teams should become cocreators of value.
17. The Role of the CIO Is Expanding
The CIO was historically responsible for internal technology operations. The future role is broader.
Technology leaders may now influence:
- Enterprise strategy
- Business-model innovation
- Product development
- Customer experience
- Workforce transformation
- AI governance
- Ecosystem partnerships
- Cyber resilience
McKinsey’s current research notes that technology leaders in high-performing organizations are more deeply involved in enterprise strategy than their peers.
The CIO must become:
- Technology strategist
- Workforce architect
- Business partner
- Risk leader
- Platform builder
- Ecosystem orchestrator
- Change leader
18. The Workplace Is Becoming Relationship-Oriented
The future workplace is not simply remote or office-based. It is a system that supports different types of interaction.
Some activities work well remotely:
- Focused coding
- Documentation
- Research
- Asynchronous review
Some benefit from real-time collaboration:
- Product discovery
- Architecture decisions
- Complex incident response
- Team formation
- Mentoring
- Conflict resolution
Deloitte describes the technology workplace as moving from location-centered design toward relationship-centered design. The relevant question becomes which environment best supports collaboration, productivity, and cocreation.
19. Hybrid Work Requires Intentional Design
A poorly designed hybrid model can create:
- Unequal access to information
- Meeting overload
- Isolation
- Weaker mentoring
- Reduced visibility
- Fragmented decisions
A strong hybrid model defines:
- Which work is asynchronous
- Which meetings require real-time attendance
- When teams gather physically
- How decisions are documented
- How remote participants are included
- How junior employees receive mentorship
The objective is not to reproduce office work through video calls. It is to redesign collaboration around the work.
20. AI Agents Are Becoming Part of the Workplace
The workplace now includes nonhuman participants.
An AI agent may:
- Attend a workflow through software integrations
- Prepare meeting summaries
- Search organizational knowledge
- Monitor systems
- Assign work
- Draft documents
- Execute approved actions
Organizations need etiquette and governance for this environment.
Questions include:
- Should employees be told when an agent produced content?
- Can agents participate in confidential meetings?
- Who approves agent actions?
- How are errors corrected?
- Can one agent delegate to another?
- How is agent identity represented?
These are workplace-design issues as much as technology issues.
21. Performance Measurement Must Change
Traditional technology metrics often focus on activity:
- Tickets closed
- Projects delivered
- Code produced
- Systems maintained
- Budget spent
These metrics can encourage volume without value.
Future measurement should include:
- Customer outcomes
- Revenue impact
- Reliability
- Security
- Time to market
- Employee productivity
- User satisfaction
- Cost per transaction
- Learning speed
- Quality of decisions
Deloitte recommends shifting governance and performance measurement toward value realization and shared business outcomes.
22. Productivity Cannot Be Measured by AI Usage Alone
A company may measure:
- Number of AI users
- Prompts submitted
- Lines of AI-generated code
- Agent tasks completed
These figures describe activity. They do not prove value.
Better questions include:
- Did software reach customers faster?
- Did quality improve?
- Did defects decline?
- Did employees spend less time on repetitive work?
- Did operating costs decrease?
- Did security risk increase?
- Did customer satisfaction improve?
AI adoption is not the objective. Improved outcomes are the objective.
23. Culture Becomes a Technology Capability
Technology transformation can fail because of cultural barriers such as:
- Fear of experimentation
- Departmental protection
- Blame after incidents
- Resistance to transparency
- Reward systems based on individual control
- Leadership that demands innovation but punishes failure
The World Economic Forum found that organizational culture and resistance to change were the second most frequently cited barriers to transformation after skill gaps.
A future-ready technology culture supports:
- Learning
- Experimentation
- Psychological safety
- Accountability
- Collaboration
- Customer focus
- Responsible risk-taking
24. Human Skills Become More Valuable, Not Less
As machines become more capable technically, human differentiation may shift toward:
- Judgment
- Creativity
- Empathy
- Communication
- Leadership
- Ethics
- Context
- Negotiation
- Curiosity
The World Economic Forum continues to identify technology skills as rapidly growing in importance while also emphasizing analytical thinking, resilience, leadership, and collaboration.
A future technology professional may therefore need a T-shaped capability profile:
- Deep expertise in one or more technical areas
- Broad ability to understand business, customers, teams, and risk
25. Governance Must Keep Pace With AI-Enabled Work
Human-agent teams create new risks.
Governance should address:
- Approved AI tools
- Data access
- Intellectual property
- Security
- Model accuracy
- Bias
- Human approval
- Audit trails
- Accountability
- Vendor dependence
Controls should be proportional to risk. An AI agent drafting internal documentation does not require the same oversight as an agent changing production infrastructure or approving financial transactions.
26. A Practical Transformation Framework
Deloitte proposes an Imagine, Compose, and Activate process for future-of-work transformation. The model can be adapted to the current AI environment. Phase 1: Imagine Describe the organization three to five years ahead.
Ask:
- What products and services will technology enable?
- Which work will AI perform?
- Which decisions remain human?
- What capabilities create competitive advantage?
- How will customers experience the company?
Do not begin by preserving the current org chart. Phase 2: Compose Design the future system.
Determine:
- Work outcomes
- Task division
- Roles
- Skills
- Team structures
- External talent
- AI agents
- Workplace patterns
- Governance
Phase 3: Activate Begin with focused changes.
Examples include:
- Redesigning one product team
- Introducing an internal developer platform
- Creating an AI-enabled support workflow
- Replacing one static role description with a skills canvas
- Launching an apprenticeship
- Renegotiating a vendor relationship
Measure results and adjust.
27. A 12-Month Action Plan
Months 1 to 3: Diagnose
- Map critical technology outcomes.
- Identify major task groups.
- Measure talent and skills.
- Inventory AI and automation tools.
- Review external providers.
- Analyze workplace friction.
Months 4 to 6: Design
- Select pilot teams.
- Define human-agent responsibility.
- Create role canvases.
- Establish AI governance.
- Design learning pathways.
- Define outcome metrics.
Months 7 to 9: Pilot
- Launch human-AI workflows.
- Train managers.
- Improve developer experience.
- Test new team structures.
- Collect employee and customer feedback.
Months 10 to 12: Scale
- Expand successful pilots.
- Stop low-value experiments.
- Update career paths.
- Modify vendor contracts.
- Revise workforce plans.
- Establish quarterly review.
28. Common Mistakes
Starting with tools Buying AI technology before redesigning work usually produces scattered experimentation. Automating broken processes Automation can make an inefficient process fail faster. Treating AI only as a cost-reduction program This can create resistance and miss opportunities for better products and decisions. Eliminating junior roles without rebuilding development pathways This weakens the future leadership and expertise pipeline. Measuring activity instead of outcomes More code or more prompts do not automatically produce more value. Outsourcing strategic capability Companies can become unable to evaluate their own systems and providers.
Redesigning the workplace without redesigning work Office policies cannot solve unclear roles, poor management, or weak collaboration.
Key Takeaways
1. Technology has moved from supporting the business to becoming part of the business.
2. The future should be designed across work, workforce, and workplace together.
3. Leaders should define outcomes before changing jobs, headcount, or office arrangements.
4. AI changes tasks more quickly than it eliminates complete occupations.
5. Human contribution will shift toward judgment, architecture, relationships, risk, and problem definition.
6. Technology organizations are moving from projects toward persistent products and value streams.
7. Human-agent teams require explicit accountability, access controls, and quality standards.
8. Technical professionals will need stronger business understanding and human capabilities.
9. Junior career pathways must be redesigned as AI takes on routine entry-level tasks.
10. Static job descriptions should evolve into flexible skills and outcome profiles.
11. Learning must occur continuously within real work.
12. Technology talent will come from employees, contractors, partners, providers, communities, and AI systems.
13. Vendor strategy is now part of workforce and capability strategy.
14. The future workplace should be designed around relationships and collaboration, not only location.
15. Technology performance should be measured by business, customer, security, and reliability outcomes.
Frequently Asked Questions
What does the future of work in technology mean?
It refers to how technology work, roles, skills, teams, workplaces, and leadership are changing because of AI, automation, cloud computing, new talent models, and closer integration between business and technology.
What are the three dimensions of future work?
They are:
- Work
- Workforce
- Workplace
Will AI replace technology workers?
AI will automate or assist many tasks, but demand will remain for people who design systems, exercise judgment, understand customers, manage risk, and coordinate complex human-machine work.
Is technology employment still growing?
Yes. The US Bureau of Labor Statistics projects computer and information technology occupations to grow much faster than the average for all occupations between 2024 and 2034.
Which technology jobs are most vulnerable to AI?
Tasks that are routine, repeatable, well-defined, and easy to verify are generally more exposed. Complete roles may change rather than disappear.
Which skills will become more valuable?
Important capabilities include:
- AI literacy
- Architecture
- Cybersecurity
- Data engineering
- Product management
- Business understanding
- Communication
- Judgment
- Leadership
- Learning agility
What is a human-agent team?
It is a team in which employees collaborate with AI agents that perform or coordinate defined work.
What is a product operating model?
It organizes persistent teams around continuing products, services, platforms, or customer outcomes rather than temporary technology projects.
What is a job canvas?
It is a flexible role profile that describes outcomes, responsibilities, changing skills, collaboration, and how automation affects the work.
Will companies need fewer junior developers?
Some organizations may hire fewer junior developers for routine coding. However, they will still need deliberate pathways for developing future senior professionals.
What is developer experience?
Developer experience describes how easily technology professionals can build, test, deploy, and operate software within an organization.
Should every company build AI capability internally?
Companies should maintain internal ownership of capabilities central to strategy, risk, architecture, data, and competitive advantage. Standardized capabilities may be purchased externally.
How should AI productivity be measured?
By improvements in:
- Time to market
- Quality
- Reliability
- Cost
- Customer experience
- Employee capacity
- Business outcomes
Will remote work remain common in technology?
Distributed work is likely to remain important, but organizations will vary. The more useful question is which environment best supports each type of work.
What should happen in person?
Activities that may benefit from physical interaction include:
- Team formation
- Complex design
- Mentoring
- Conflict resolution
- Strategic planning
- Intensive collaboration
What is the role of the CIO in the future?
The CIO increasingly acts as a business strategist, workforce architect, AI leader, platform builder, risk executive, and ecosystem coordinator.
How should companies begin transforming technology work?
They should:
1. Define business outcomes.
2. Break work into tasks.
3. Decide how people and AI divide the tasks.
4. Identify required skills.
5. Pilot new team and workplace models.
6. Measure outcomes.
7. Adjust continuously.
Conclusion
The future of work in technology is not primarily a debate about offices, job losses, or individual AI tools. It is a redesign of how organizations create value. Technology is spreading beyond the traditional IT function and becoming inseparable from products, operations, customer experiences, and strategy. AI is changing the economics of execution. It can generate, analyze, test, monitor, summarize, and coordinate at extraordinary speed. But organizations still need people to decide what matters. They need people to understand customers, define problems, design systems, manage risk, build trust, evaluate tradeoffs, and accept accountability. The future technology organization will therefore not be composed only of employees, and it will not be operated only by machines.
It will be a connected system of:
- Internal professionals
- Business experts
- External specialists
- Technology providers
- Platforms
- Automation
- AI agents
The quality of that system will depend on how intentionally it is designed. Companies should begin with work outcomes. They should identify the tasks required to produce those outcomes. They should assign each task to the person, team, platform, or agent best suited to perform it. They should create career pathways that allow people to grow as routine work changes. They should build workplaces that support collaboration regardless of location. They should measure business value rather than technology activity. The most successful organizations will not be those that employ the most technologists or deploy the most AI agents. They will be the organizations that combine human judgment and technological capability most effectively.
The defining question is no longer:
What will technology do to the workforce?
It is:
What kind of work, workforce, and workplace should we deliberately create now that people and intelligent systems can accomplish more together than either could accomplish alone?
Relevant Articles and Resources
1. The Future of Work in Technology
Deloitte Insights
The foundational work, workforce, and workplace framework used as the conceptual starting point for this article.
2. Designing an End-to-End Technology Workforce for the AI-First Era
McKinsey & Company
A 2026 analysis of technology hiring, internal capability development, vendor strategy, and human-agent teams.
3. The Future of Jobs Report 2025
World Economic Forum
https://www.weforum.org/publications/the-future-of-jobs-report-2025/
Global research on job transformation, skills, AI adoption, talent availability, and employer workforce strategies.
4. Computer and Information Technology Occupations
US Bureau of Labor Statistics
https://www.bls.gov/ooh/computer-and-information-technology/
Official US employment outlook and wage data for technology occupations.
5. The Agentic Organization: Contours of the Next Paradigm for the AI Era
McKinsey & Company
A framework for redesigning business models, operating models, governance, workforce, culture, technology, and data around agentic AI.
6. Superagency in the Workplace: Empowering People to Unlock AI’s Full Potential
McKinsey & Company
Research on how organizations can amplify human agency and employee productivity through AI.
7. How AI Is and Isn’t Changing the Future of Work
McKinsey & Company
A current perspective on how AI changes work while many fundamental employee expectations remain consistent.
8. Future of Work
McKinsey & Company
https://www.mckinsey.com/featured-insights/future-of-work
A collection of research on automation, workforce transitions, skills, organizational design, and changing workplaces.
9. The State of Organizations 2026
McKinsey & Company
Research on AI, organizational complexity, human-agent collaboration, resilience, and enterprise transformation.