{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/bac5703ec71a46bfb9e32cce468a6cb5\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/bac5703ec71a46bfb9e32cce468a6cb5-78b3e81e9483c317.gif","duration":133.508,"title":"Introduction To T.I.M.E. Framework","description":"This Loom argues that engineering orgs need to be built to run without the CTO, because stalls and escalations after stepping back are a structural issue. It explains how leaders gravitate back to the work they know at each promotion from engineer to manager to director to VP to CTO, causing the CTO to stay in the weeds while delivery pauses. The speaker contrasts this with the “engineering flywheel,” driven by great people, motivated teams, operational success, and a strong culture for innovation and fewer escalations. The Loom concludes that accelerating the flywheel requires CTO strategic focus through time allocation, leadership bench building, scaling the org, and influencing priorities, aiming for a truly strategic CTO."}