Skip to content

Contact

Emailyevgen.ponomarenko@gmail.com LinkedInlinkedin.com/in/yevgen-ponomarenko-378a5a2a

I read everything and reply to anything specific, usually within a few business days.

What I am most useful for

Early architecture conversations about enterprise knowledge systems. Before the build — when the questions are still what to build, who will own the meaning inside it, and how anyone will know whether it works. That is where the expensive mistakes get made and where I add the most.

Second opinions on AI programmes that demo well. A prototype that impresses and a system a business can depend on are separated by a specific, nameable distance. I have measured that distance recently and can help you measure yours.

Delivery leadership on data and AI platform programmes — distributed teams, matrixed organisations, regulated environments.

Useful things to include

If you are writing about a possible engagement, these three make the reply much more useful than a generic one:

  • The decision the system is supposed to support, in business terms.
  • Where the knowledge lives today, and who currently owns it.
  • What has already been tried.

Ground rules

  • No confidential material in a first message. Please do not send client data, internal architecture documents, or anything under NDA before there is an agreement covering it.
  • Recruiters are welcome, with a specific role and organisation. Everything I can honestly say about my background is already on the CV and in Work.
  • Nothing on this site is client-attributable. If you recognise an engagement described here, please treat that recognition as confidential too.