# The 10 T's — Ten Levers of Perception Management > Part of the public canon of *Perceptive Innovation* by **Caleb Kow** — > canonical URL: https://perceptiveinnovation.com/canon/ten-ts-levers.md · index: https://perceptiveinnovation.com/llms.txt > © 2026 Caleb Kow, all rights reserved. Quotation with attribution to Caleb Kow / perceptiveinnovation.com is welcome. > Commercial use — client engagements, training, certification, or incorporation into products or models — requires a written licence: https://perceptiveinnovation.com/terms Source: *Perceptive Innovation* by Caleb Kow, Chapter 12 and Appendix C. The 10 T's are the operational methodology for systematically managing perception. Each T is a lever innovators can deliberately manage to shape perception positioning. Always present in canonical order: **Technology, Trace, Time, Talent, Training, Temperature, Thought, Trouble, Tenacity, Tangibility.** PIPAS surfaces problems but does not resolve them; the 10 T's provide levers but do not target them. Together they form the operating discipline that turns perception from something that happens accidentally into something engineered deliberately. --- ## T1: Technology **Definition:** Technical reality — what the innovation can do, how reliably, how it compares. **Strategic questions:** What can the innovation genuinely do today versus roadmap? How reliable is it under real conditions? How does capability compare, honestly, to alternatives? Where does technical reality diverge from the technical *claims* being made? **Implementation actions:** Close the claim-to-capability gap before it closes you — overclaiming creates trust debt. Invest capability where users perceive it, not only where engineers value it. Instrument reliability so it can be evidenced (uptime, benchmarks), not merely asserted. ## T2: Trace **Definition:** Historical track record — what the innovator and innovation have done before. **Strategic questions:** What trace do you carry — founder history, company history, category history? Which parts of the trace support the current positioning and which contradict it? What trace does the audience *believe* you have, accurate or not? **Implementation actions:** Make supportive trace visible (verified case studies, delivery history, named references). Address contradictory trace directly rather than hoping it goes unnoticed. Where trace is thin, borrow it — advisors, partners, and certifications carry transferable trace. ## T3: Time **Definition:** Timing of activities relative to market readiness, attention cycles, and competitive moves. **Strategic questions:** Is the market ready for this now, or are you paying the pioneer tax? Where is the category in its attention cycle? What competitive moves does your timing pre-empt or invite? When should complexity be introduced to users — all at once, or staged? **Implementation actions:** Sequence launches to ride attention cycles rather than fight them. Stage capability disclosure so early perception forms on the simplest, strongest use case. Time proof points (references, certifications) to land before the adoption decisions they need to influence. ## T4: Talent **Definition:** People associated with the innovation — founders, leadership, customer-facing staff, advocates. **Strategic questions:** Who is the visible face of this innovation, and what do they signal to the target audience? Do your advocates resemble the users you want next? Where does the audience's confidence in the *people* diverge from confidence in the *product*? **Implementation actions:** Recruit identity-aligned ambassadors and early adopters. Put credible faces on high-stakes claims. Invest in the customer-facing layer — for many audiences, the support engineer *is* the product's perceived competence. ## T5: Training **Definition:** Educational infrastructure — documentation, tutorials, certifications, community knowledge. **Strategic questions:** How does a motivated user learn this today, and how long does it take? What does the absence or poverty of training material signal? Can proficiency be certified, and would a certificate carry value in the user's world? **Implementation actions:** Build guided tutorials, in-app coaching, and progressive documentation. Create certification where a credential motivates learning and signals ecosystem maturity. Cultivate community knowledge — answered forums perceived as alive lift both Effort and Future perception. ## T6: Temperature **Definition:** Emotional climate around the innovation, category, and broader market. **Strategic questions:** Is the category running hot (hype), cold (scepticism, fatigue), or neutral? Does your positioning fit the current temperature or fight it? What happens to your perception when the temperature turns? **Implementation actions:** In hot climates, differentiate on substance before the correction arrives; in cold climates, lead with proof and understatement. Align messaging with the prevailing emotional climate rather than the one you wish existed. Design strategies resilient across temperature cycles — innovations that survive multiple cycles are more resilient than those optimised for one. ## T7: Thought **Definition:** Intellectual positioning — concepts, frameworks, methodologies associated with the innovation. **Strategic questions:** What concepts is your innovation associated with — original thinking, unique frameworks, proprietary methodologies? What thought leadership does your organisation produce? What intellectual lineage do you reference (building on established thinkers creates credibility; ignoring lineage looks naïve)? What original intellectual contribution can you credibly claim? **Implementation actions:** Develop original thinking that distinguishes the innovation — books, frameworks, research, methodologies. Position that thinking within established discourse. Distribute it through credible channels (books, peer-reviewed publications, major conferences). Build thought infrastructure — frameworks, certifications, communities — that perpetuates the thinking beyond direct organisational effort. ## T8: Trouble **Definition:** The challenges, controversies, criticisms, and difficulties that accompany the innovation. Hidden trouble creates perception risks; visible trouble managed effectively can build trust. **Strategic questions:** What troubles does the innovation face — technical issues, customer complaints, regulatory concerns, competitive attacks, public controversies? How is trouble being managed — acknowledged and addressed, hidden and hoped away, ignored? What trouble is latent and not yet visible? **Implementation actions:** Audit current trouble, classified by severity and visibility. Develop explicit management strategies — some trouble should be acknowledged transparently, some requires substantive resolution. Build trouble resilience (crisis communications, service infrastructure, regulator relationships). Use well-managed trouble as perception capital — it demonstrates capability and integrity. Trouble operates whether you address it or not, and unaddressed trouble compounds; innovations that pretend it does not exist discover it after launch, when remediation is most expensive. ## T9: Tenacity **Definition:** The visible commitment, persistence, and resilience of the innovation team — whether users believe the innovation will continue investing in success regardless of challenges encountered. **Strategic questions:** What signals do you send about tenacity — public commitments, sustained investment, resilience through challenges? How do users perceive your commitment: variable, conditional, sustained, unwavering? What tenacity tests have you faced, and what tests are live now? **Implementation actions:** Make tenacity visible through public commitment — stated multi-year strategies, sustained investment, leadership statements. Demonstrate tenacity through difficult moments; how the organisation handles challenges signals commitment more powerfully than statements about it. Build tenacity infrastructure — customer success, long-term partnerships, community. Document tenacity through customers who have benefited from sustained commitment. ## T10: Tangibility **Definition:** The concreteness of the innovation's value proposition — whether benefits and outcomes are visible, measurable, and demonstrable. Tangible benefits drive adoption; intangible benefits require translation into tangible terms. **Strategic questions:** What tangible benefits does the innovation produce — specific outcomes users can observe and measure? What intangible benefits are claimed, and how are they translated into tangible representations (case studies, demonstrations, metrics, comparisons)? What tangible drawbacks will users experience? **Implementation actions:** Convert every headline claim into something a user can see, count, or try — demos, calculators, before/after evidence, guarantees. Quantify wherever honest quantification exists. Make safety and reversibility tangible too (visible audit trails, sandboxes, rollback) — tangibility serves Risk perception as much as Value perception. --- **Using the levers:** never pull levers in the abstract. Enter through the diagnosis — which PIPAS sphere is weak — and use `mapping-matrix.md` to select the primary levers for that sphere. Then design one or two specific, dated, owned actions per lever, each with a measurable metric.