Outdoor portrait of Oleg Gaidukov
Oleg Gaidukov.

ABOUT ME

Oleg Gaidukov

Operational CTO

I build product and engineering teams from scratch and work with existing ones. Together, we work through a technical problem, choose a change and put it into practice to check the result.

Selective engagements ยท EMEA / Remote

When I get involved

I get involved when an important technical decision is stuck. Responsibility is split, the data is hard to interpret, and waiting costs more each day. I help the team choose a change it can test and agree on who will keep it working.

How I work

  1. Work out what needs to be decided

    First, I separate facts from assumptions and work out what's limiting us. Then I discuss the decision with the people who will answer for it. We write down what we decided and why.

  2. Put the change into practice

    An agreement with leadership still needs to work in the system. I work through the architecture, code and release process, checking logs and safeguards along the way. The team needs to be able to inspect the result.

  3. Hand the work over to the team

    Before handover, we need measurements to compare against and someone on the team responsible for the work. If the team depends on me indefinitely, I've done this badly. An urgent start doesn't excuse that.

What guides my work

  • Start with the decision

    Work out what needs to be decided and which facts are missing before adding another meeting.

    Read more
  • Direct communication

    Be clear about what we know and what we're assuming. Name the person responsible for the next step.

    Read more
  • Test a small change

    Agree on one change and its scope. Compare the result with the starting measurements or an agreed indirect measure when a direct one isn't available.

    Read more
  • Follow through on the decision

    The work isn't finished until the decision changes the architecture, code, release process or safeguards.

    Read more
  • Be clear about the trade-offs

    Discuss what we'll gain and what we'll give up, especially when the team has to live with the consequences.

    Read more
  • Have a person check risky decisions

    When a system's mistake could cost too much, a person must check the decision.

    Read more

What we agree upfront

  • I publish results only with a source and permission. I state my role and what the evidence can support.
  • I don't offer free diagnosis or join simply as an extra team member. Innovation work needs a defined scope and an end.
  • Before we start, we agree on who in the team will take responsibility and how we will hand over the work.