Eleven Checklists Take a Search From Opening to the First Year

These checklists take a search from opening to the first year. Check each statement that is true today; a statement you cannot check is a gap to close before the next stage.

Do Not Open the Search Until These Fifteen Things Are True#

• The business reason for the role is written in one paragraph.
• Alternatives to a CTO hire were considered.
• The base role and overlays are named.
• Three to five first-year outcomes are defined.
• Scope and important exclusions are explicit.
• Decision rights use precise verbs.
• The CTO, CIO, CPO, CISO, and VP Engineering boundaries are clear where relevant.
• A founder transition is decided before candidates are asked to accept it.
• Fractional, interim, and full-time models were compared.
• The reporting line, budget, and board access are real.
• The decision owner and required approvers are named.
• The hiring scorecard has no more than seven criteria.
• Each criterion links to evidence and an interviewer.
• Candidate information and confidentiality are planned.
• HR and legal have reviewed the process.

Stop the search if the company cannot explain why the role exists, what it can decide, or which existing executive relationship will change.

Screen Candidates on Their Actual Work#

• Candidate’s actual work is understood beyond title.
• Relevant mission evidence is present.
• Company-stage and resource differences are visible.
• Candidate wants the work, not only the title.
• Candidate names the least familiar part of the role.
• Candidate asks useful questions about business, team, risk, and authority.
• No necessary criterion is replaced by pedigree.
• Domain experience is separated from actual decision responsibility.
• Motivation and timing are discussed directly.
• Compensation, location, and transition expectations are plausible.
• Evidence gaps are recorded for later testing.

Run Structured Interviews Against the Criterion#

• Interviewer knows the criterion and does not improvise a different job.
• Questions seek past evidence before hypothetical confidence.
• Follow-ups test context, options, contribution, result, and learning.
• Technical depth matches the role altitude.
• Candor includes the candidate’s own mistake or late news.
• Influence evidence includes decisions the candidate did not control.
• Delegation evidence shows a mechanism and transfer.
• Notes separate candidate statement, observation, and inference.
• Candidate receives time to ask questions and challenge the mandate.
• No one asks for protected, private, or irrelevant personal information.

Check Finalists Before You Trust the Story#

• Work sample is relevant, bounded, and not free consulting.
• Candidate has enough truthful company information.
• Known risks and inherited conditions are disclosed.
• Founder or outgoing-leader role is explicit.
• References cover manager, peer, direct report, or other relevant positions.
• Critical claims are targeted in references.
• Conditions behind past success are documented.
• Technical or domain responsibility is confirmed where material.
• Conflicting evidence is investigated rather than averaged.
• Candidate-proposed mandate changes are considered.
• The hiring-bet memo can be written honestly.

Settle Terms and Boundaries Before Acceptance#

• Final mandate reflects negotiations.
• Reporting line and executive status are confirmed.
• Scope, team, budget, and hiring assumptions are recorded.
• Board, customer, or external role is explicit.
• Equity, compensation, benefits, severance, and change-of-control terms receive qualified review.
• Intellectual property, confidentiality, conflicts, and outside activity are addressed.
• Promised complementary hires or founder boundaries are recorded.
• Start date, communication, and transition are planned.
• Known risks have support and review dates.
• Other candidates are closed respectfully.

In the First 30 Days, Learn Before You Reorganize#

• Entry brief is complete and curated.
• Access and introductions are ready.
• Urgent decisions and decisions that can wait are separated.
• CEO-CTO weekly cadence begins.
• Customers and frontline operations are included in learning.
• Technical contact includes direct observation, not only presentations.
• Risks are described with evidence and consequence.
• No broad reorganization or rewrite begins without sufficient evidence.
• Day-30 mandate assumptions are reviewed.
• Company commitments and authority gaps are corrected.

By Day 90, Name the Agenda and What Will Stop#

• Business and customer model can be explained plainly.
• Material technical and organizational constraints are clearer.
• Urgent decisions show a sound method.
• Leadership assessment is fair and specific.
• Twelve-month agenda has five or fewer outcomes.
• Work that will stop is named.
• Decision mechanisms have owners and purpose.
• Executive relationships contain clear conflict paths.
• CTO has corrected at least one hiring assumption where evidence required it.
• Company has reviewed its own fulfilled and unfulfilled commitments.

By Day 180, Important Decisions Move Earlier#

• Important decisions move earlier and at the right level.
• At least one new mechanism has been traced through real cases.
• Bureaucracy has been removed where it adds no value.
• Leadership changes or support are underway.
• Programs have internal customers, capacity, and stop rules.
• Fractional or interim work is transferring internally.
• Founder and incoming-CTO boundaries operate in practice.
• Unit and enterprise dependencies have service or escalation rules.
• Risks are accepted by the proper authority.
• Agenda items are stopped, continued, narrowed, or accelerated based on evidence.

At One Year, Judge Whether the Capability Is Sustainable#

• Business outcomes and technology contribution are assessed carefully.
• Delivery capability is more sustainable, not merely faster for one quarter.
• Reliability, security, safety, or resilience risk is better controlled and visible.
• Cost and capital decisions are clearer.
• The company is easier to change where strategy requires it.
• Leadership capability exists beyond the CTO.
• Material decisions have better evidence and escalation.
• Bad news reaches executives early enough.
• The hiring-bet assumptions and risks are reviewed honestly.
• The role is confirmed, evolved, complemented, or changed.
• Next-year outcomes replace rather than accumulate on the old agenda.
• Succession and emergency coverage are updated.

A Fractional Engagement Needs a Charter and an Exit#

• Charter names outcomes and decisions, not only hours.
• Availability and emergency coverage are explicit.
• Internal execution owner has authority.
• Vendor and investment conflicts are disclosed.
• Company data and access are protected.
• Recommendations, decisions, and acceptance are recorded.
• Internal capability transfer is measured.
• Full-time trigger is defined.
• Engagement cannot extend automatically without outcome review.
• Handover and exit artifacts are required.

A Founder Transition Needs Precise Rights and Real Work#

• Future company need is separated from past contribution.
• Founder has stated preferred future work.
• Board and legal process are appropriate.
• Role options include remain, complement, reposition, and exit.
• New decision rights are precise.
• Founder has a real role or no operating role, not a ceremonial shadow position.
• Direct reports and private escalation are addressed.
• Knowledge and external relationships are mapped.
• Internal and external communication is consistent.
• Incoming candidates receive the truth.
• CEO will enforce the boundary.
• Review dates test whether the structure works.