What this page covers
This page explains the relationship between TI and Do, focusing on how they compare, overlap, and where they diverge. It is written to help readers understand the practical implications of TI and Do for planning, procurement, and day‑to‑day decisions. We present definitions, typical use cases, and the consequences of choosing one approach over the other without speculative claims or time‑sensitive references.
Core definitions and framing
TI commonly denotes technology‑ or infrastructure‑focused initiatives, often tied to systems, platforms, and long‑term capability building. Do represents action‑oriented workstreams, delivery units, or operational practices that emphasize execution and measurable outputs. Both address organizational needs but do so at different layers of abstraction and timelines. Clarifying which term refers to which scope in your context is essential to avoid misalignment.
Where TI and Do align
In many programs, TI and Do coexist as complementary strands. TI sets the architecture, standards, and foundations; Do applies those foundations to deliver services, products, or improvements. When governance is clear, TI can guide Do so that actions remain consistent with long‑term objectives, while feedback from Do can refine TI roadmaps. Alignment mechanisms such as shared metrics, integrated roadmaps, and cross‑functional teams help realize this synergy.
Shared outcomes that matter
- Improved decision quality through reliable data and clear criteria.
- Consistent user and stakeholder experience across touchpoints.
- More predictable timelines and budget performance when plans are synchronized.
Key distinctions between TI and Do
TI tends to emphasize design, interoperability, and future scalability, often requiring upfront investment and longer horizons. Do focuses on execution, local optimization, and immediate results, with shorter feedback loops. Understanding these distinctions helps teams decide where to centralize standards and where to allow decentralized action.
| Attribute | TI (typical emphasis) | Do (typical emphasis) | Source Type |
|---|---|---|---|
| Primary focus | Architecture, standards, long‑term coherence | Execution, delivery, immediate outcomes | Common industry usage |
| Time horizon | Multi‑year roadmap | Current sprints and quarters | Planning practice norms |
| Success metric | Adoption, integration, reuse | Delivery rate, cycle time, quality | Operational benchmarks |
| Governance style | Centralized standards and review | Delegated execution with local adaptation | Typical program governance models |
Practical implications for planning and procurement
When TI and Do are treated as separate but linked layers, planning can become more modular. Procurement can distinguish between commitments that lock in foundational capabilities (TI) and those that focus on service delivery and performance (Do). This distinction reduces risk by clarifying ownership, change management, and budgeting responsibilities across the lifecycle.
Implications to consider
- Clarity on who decides scope changes at the architectural versus delivery level.
- Separate but aligned KPIs for infrastructure health and delivery throughput.
- Joint governance forums to surface dependencies early and resolve conflicts.
Common challenges and mitigations
Organizations sometimes experience tension when TI teams prioritize standardization and Do teams prioritize speed. Misalignment can surface as duplicated effort, integration debt, or unclear accountability. Mitigations include shared roadmaps, explicit integration milestones, and lightweight contracts that allow Do to adopt TI components while providing feedback for evolution.
How to decide which layer applies in a given situation
Use a simple set of cues: if the issue affects multiple teams, requires long‑term coherence, or involves platform economics, TI considerations typically lead. If the issue is time‑bound, localized, and outcome‑driven, Do practices often guide the response. Documenting these cues in a decision framework makes tradeoffs transparent and repeatable.
Next steps for clarifying TI–Do relationships in your organization
Start by mapping current initiatives to TI and Do roles, stating clear owners and decision rights for each. Define shared outcomes, align roadmaps at least annually, and establish joint ceremonies for dependency management. Treat TI and Do as mutually reinforcing rather than competing, and iterate the balance as your context evolves.
Summary and key takeaways
- TI and Do serve different but compatible purposes in most programs.
- Alignment around shared metrics and roadmaps reduces friction and improves outcomes.
- Understanding the primary emphasis of each helps with prioritization and governance.
- Practical planning benefits from separating foundational commitments (TI) from execution commitments (Do).
- Explicit decision rules make it easier to manage tradeoffs over time.