Superculture

About

You should not have to explain the problem twice. That continuity is why Superculture is principal-led.

The person who helps you make the original decision should still be in the room when the data turns out to be messier than advertised, when the implementation surfaces an awkward exception, when a priority shifts, or when a release misbehaves at nine on a Friday. Most firms treat that continuity as a luxury. We treat it as the product.

01

Tarikh Korula speaking onstage at a lectern

Tarikh Korula

Tarikh has spent twenty-five years building technology products, raising capital, building teams and growing users. He remembers when AI was still machine learning and natural language processing, founding an AI company in 2014, ten years too early (Wired). He loves the space.

In addition to building companies, Tarikh coaches founders. He started coaching first with Reboot before launching his own boutique practice focused on leadership excellence and mindfulness. He has partnered with On Deck, Hampton and Sanity Labs along the way to coaching over 120 ventured-backed startup CEOs and CTOs, VPEs and Heads of Product. His background gives him a unique skillset for this next era of business strategy and AI implementation.

Strategy, engineering, and the human being carrying both. AI work that reaches production refuses to stay inside any one of those categories, and so does he.

02

How specialists join.

Some problems want more hands than one principal: a focused engineer, a product operator, a designer, a researcher, a domain expert. They join for a defined part of the work, you know who they are and why they are there, and they plug into an engagement that already understands your problem. What never happens is the quiet handoff, where the person who heard you is replaced by someone who has read a summary of you.

03

What remains with the principal.

  1. Hearing the problem firsthand.
  2. Forming, and revising, the point of view.
  3. Making the important tradeoffs visible.
  4. Connecting the strategic and technical decisions.
  5. Staying present for review, release, and what the team learns.
  6. Answering for the coherence of the whole engagement.

Public record.

SEEN — Wired →
Ed Batista on Ed Bot — edbatista.com →
Open-source Founder CoS work — GitHub →
Tarikh's independent coaching site — tarikhkorula.com →
LinkedIn — LinkedIn →
Read the work Talk to us