{"product_id":"my-it-director-is-lying-to-me-about-everything-what-do-i-do","title":"My IT Director Is Lying To Me About Everything. What Do I Do?","description":"\u003cp\u003e\u003cstrong\u003eLaunching June 15, 2026.\u003c\/strong\u003e This is the kitchen's first buyable product. Notify list opens now; orders open June 15.\u003c\/p\u003e\n\n\u003chr\u003e\n\n\u003cp\u003e\u003cem\u003ethe five-second epistemology of: your IT director is lying · the data lake is a stalling tactic · digital transformation is a roadmap to nowhere · the integration is fine, the integration was always fine · the in-house build is a job-protection scheme · ninety percent of the team's hours are not on the critical path · the writing test is the entire game · and when he pivots into gratitude, the smoke and mirrors meeting is on its way\u003c\/em\u003e\u003c\/p\u003e\n\n\u003ch3\u003eFREE ADVICE FIRST. DO NOT HIT BUY.\u003c\/h3\u003e\n\n\u003cp\u003eWhatever your IT director just told you, assume he is lying.\u003c\/p\u003e\n\n\u003cp\u003eThis is the free advice. the kitchen gives it away because the kitchen does not need your money for the part you can solve yourself.\u003c\/p\u003e\n\n\u003cp\u003eHe told you the systems do not talk to each other. The systems talk to each other. He told you the build will take six months. The build is a Google Sheet. He told you the team is fully utilized. The team is in a Slack channel arguing about kanban columns. He told you the new platform is critical. The new platform is the same platform with a new vendor and a different invoice cycle. He told you the data lake is the foundation. The data lake is a place to put data so the data can sit there. He told you the digital transformation is on schedule. The digital transformation is a Gantt chart that will be revised before the next board meeting. He told you the integration is the bottleneck. The integration was solved by Zapier in 2014.\u003c\/p\u003e\n\n\u003cp\u003eSay no. To the new tool. To the in-house build. To the pilot program. To the consultant scoping engagement. To the data warehouse migration. To the \"exploring AI\" budget request. To the headcount expansion. To the off-site planning workshop. To the architecture review board. To the modernization initiative. To the platform consolidation. To the platform diversification. To the cloud migration. To the cloud repatriation.\u003c\/p\u003e\n\n\u003cp\u003eThis works approximately ninety percent of the time. the kitchen tells you this for free because the kitchen does not believe in selling people things they do not need. The seminary believes in that. the kitchen does not.\u003c\/p\u003e\n\n\u003ch3\u003eTHE WRITING TEST\u003c\/h3\u003e\n\n\u003cp\u003eBefore you hit buy, run the writing test.\u003c\/p\u003e\n\n\u003cp\u003eTell him this is the A problem. Tell him this is the only problem. Tell him to stop working on everything else and put his analysis in writing. Not a verbal walkthrough. Not a Slack thread. Not a meeting on his calendar in three weeks. Writing. On a page. With specifics.\u003c\/p\u003e\n\n\u003cp\u003eIf he produces the writing — hit buy. Upload it. The reading lands in 48 hours.\u003c\/p\u003e\n\n\u003cp\u003eIf he produces vague writing — bullet points with no specifics, links to vendor brochures, \"we are evaluating,\" \"in alignment with our roadmap,\" \"directionally aligned with the strategy\" — hit buy. Upload it. That is the artifact the kitchen reads.\u003c\/p\u003e\n\n\u003cp\u003eIf he stalls — \"I am too busy,\" \"we should discuss this in person,\" \"let me get back to you next week\" — he is not too busy. He is protecting himself. You have your answer without paying for it.\u003c\/p\u003e\n\n\u003cp\u003eWhatever he produces, hit buy. Whatever he refuses to produce, you already have the answer.\u003c\/p\u003e\n\n\u003ch3\u003eWHY HE WILL NOT PUT IT IN WRITING\u003c\/h3\u003e\n\n\u003cp\u003eHe is not busy. He is protecting himself.\u003c\/p\u003e\n\n\u003cp\u003eHis incentive structure is the inverse of yours. He optimizes for intellectual stimulation, not business value. He wants to do the things LinkedIn says are interesting — the AI strategy, the platform modernization, the data mesh, the developer experience initiative, the observability overhaul, the zero-trust architecture migration. He does not want to do the things the business actually needs — which are usually boring, usually already solved by existing tools, usually completed in a week if anyone bothered.\u003c\/p\u003e\n\n\u003cp\u003eWriting creates evidence. Evidence creates analysis. Analysis creates the fire.\u003c\/p\u003e\n\n\u003cp\u003eHe has read this product page. He has done the math. He has decided to remain too busy.\u003c\/p\u003e\n\n\u003cp\u003eThe longer he stays too busy, the more certain the answer.\u003c\/p\u003e\n\n\u003ch3\u003eSTILL THINK YOU NEED HIM IN THAT MEETING?\u003c\/h3\u003e\n\n\u003cp\u003eWhen the ninety percent does not apply, when you actually have to sit across from him and walk him through why his last six initiatives generated zero business value, the kitchen ships the read.\u003c\/p\u003e\n\n\u003cp\u003eThe read disassembles every bullshit bullet point by name. The data lake claim — disassembled. The integration problem — named for what it is. The headcount request — translated into the operational gap it is concealing. The \"we need to build it in house\" — sourced against the three off-the-shelf products that already do what he claims is custom. The digital transformation — mapped against the transformation that already happened in the rest of the company without his department's participation. The vendor evaluation rubric — read against the kickback structure embedded in it. The \"AI strategy\" — named as the LinkedIn post it actually is.\u003c\/p\u003e\n\n\u003cp\u003eYou walk into the meeting with the read in your hand. He reads the room. He revises the roadmap. He retracts the budget request. He understands he is no longer the only person at the table who can name the architecture. the kitchen prepares you to dismiss him as the charlatan he is, with receipts.\u003c\/p\u003e\n\n\u003cp\u003e48-hour delivery. Cards included. Kitchen-grade.\u003c\/p\u003e\n\n\u003ch3\u003ePHASE TWO: THE SMOKE AND MIRRORS MEETING (INCLUDED)\u003c\/h3\u003e\n\n\u003cp\u003eThe read lands. You walk into the room with it. He reads the air. He pivots.\u003c\/p\u003e\n\n\u003cp\u003eHe does not push back. He pivots.\u003c\/p\u003e\n\n\u003cp\u003e\"Thank god you brought this up. Thank god we caught these issues now and not six months in. This is exactly the kind of pressure-testing we needed. I want to put together a blueprint. I want to run an all-hands. I want to bring the team in and walk everyone through the remediation roadmap. I want to schedule the steering committee. I want to set up a cross-functional working group. I want to circulate a Path Forward deck by Friday.\"\u003c\/p\u003e\n\n\u003cp\u003eHe is now your collaborator. He is now leading the response to the problem he created. The room is grateful. Everyone agrees it is a good thing the issues were caught when they were caught.\u003c\/p\u003e\n\n\u003cp\u003eHe is not fixing anything. He is buying time.\u003c\/p\u003e\n\n\u003cp\u003eThe blueprint is the next data lake. The all-hands is the next steering committee. The remediation roadmap is the next digital transformation. Every meeting he calls in the name of \"addressing these issues\" is another month he stays employed and another month his budget stays approved. The Path Forward deck is the Path Backward, dressed up.\u003c\/p\u003e\n\n\u003cp\u003eThe kitchen names this in advance. When phase two starts — when the calendar invite goes out for the \"remediation review,\" when the deck appears titled \"Path Forward,\" when HR refers to it as a \"constructive conversation,\" when the steering committee schedule appears — the kitchen ships a second read against the proposal. We name what each meeting is actually for, which deliverables are stalling tactics, which ones could plausibly fix something, and where the budget goes if you let any of it land.\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eIncluded. No upcharge. Same product. Same price.\u003c\/strong\u003e The smoke and mirrors meeting is the kitchen's home turf. The seminary built the smoke and mirrors meeting. the kitchen reads it for what it is.\u003c\/p\u003e\n\n\u003ch3\u003eTHE CALL ANALYSIS LAYER\u003c\/h3\u003e\n\n\u003cp\u003eIf the situation requires it, the kitchen analyzes the call. Recording, transcript, live sit-in — all on the table. the kitchen sits silently and reads the room.\u003c\/p\u003e\n\n\u003cp\u003eMost of the time the call is unnecessary. The writing is the evidence. The call is theater built around the writing. When the writing is sufficient, the kitchen reads the writing. When the writing is being actively dodged, the kitchen sits on the call and watches the dodge happen in real time.\u003c\/p\u003e\n\n\u003ch3\u003eTHE PRICE\u003c\/h3\u003e\n\n\u003cp\u003e\u003cstrong\u003e$2,994.99.\u003c\/strong\u003e A five-dollar Substack discount applied, honoring the subscription model everyone keeps asking for. The Substack-grade output remains free on X.\u003c\/p\u003e\n\n\u003cp\u003eClick. Pay. Upload the writing. Name the company. Name the IT director. Name the last three initiatives he tried to sell you. The reading lands. The smoke and mirrors meeting reading lands when it happens.\u003c\/p\u003e\n\n\u003ch3\u003eWHAT THIS PRODUCT DOES NOT INCLUDE\u003c\/h3\u003e\n\n\u003cp\u003eOne read, plus the phase-two smoke and mirrors read when it lands. That is the scope. Not included at this price:\u003c\/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eOngoing engagement or monthly retainer \u003cem\u003e(see Tier 3 — Monthly Ongoing Read)\u003c\/em\u003e\n\u003c\/li\u003e\n\u003cli\u003eMulti-target series across the buyer's full IT stack \u003cem\u003e(see Tier 2 — Series)\u003c\/em\u003e\n\u003c\/li\u003e\n\u003cli\u003eSoftware builds, dashboards, or hosted systems \u003cem\u003e(see Tier 6 — Architecture Dashboard)\u003c\/em\u003e\n\u003c\/li\u003e\n\u003cli\u003eFull operating engagement against the IT department's data \u003cem\u003e(see Tier 4 — Buyer-Data FDE Engagement)\u003c\/em\u003e\n\u003c\/li\u003e\n\u003cli\u003eDirect engagement with the IT director on the buyer's behalf\u003c\/li\u003e\n\u003cli\u003eImplementation of the kitchen's recommendations\u003c\/li\u003e\n\u003cli\u003eLegal action or HR proceedings — the read informs, the buyer acts\u003c\/li\u003e\n\u003cli\u003eReplacing the IT director — the buyer handles the firing\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003cp\u003eEverything above can be done at scope, in the right tier, for the right price. This product is scoped to the read plus the phase-two read.\u003c\/p\u003e","brand":"Bespoke Ontology","offers":[{"title":"Single Read · 48hr Delivery","offer_id":48568401690872,"sku":null,"price":2994.99,"currency_code":"USD","in_stock":false}],"url":"https:\/\/bespokeontology.com\/products\/my-it-director-is-lying-to-me-about-everything-what-do-i-do","provider":"Bespoke Ontology","version":"1.0","type":"link"}