01 / Work
Context matters.
I lead knowledge management at iwoca. I manage a team of writers and product-manage our internal Handbook, working on documentation, interface code, and the AI and analytics systems it connects to. My remit is broad: helping people find trustworthy information, share what they know, and get things done.
Across disciplines.
My Ph.D. in mechanical engineering was particularly formative. My own research brought together biology, engineering, chemistry, and imaging. Defining the questions, designing experiments, and making sense of the results taught me to work independently and explain my reasoning to people with different expertise and priorities. You can read my thesis, The Mechanical Properties of Primary Feathers PDF.
Law school added a different way to examine arguments: read closely, question assumptions, and follow the implications of the wording. I draw on both experiences when I’m working with specialists or picking up an unfamiliar problem.
That breadth has been useful in projects ranging from research communications to R&D claims. At Darktrace, I helped develop a research blog that explained the work behind its products in response to competitive criticism. I’ve also worked on R&D claims at both Darktrace and iwoca.
I also contributed to phishing protection and simulation software at Darktrace, helping draft spoofed, self-adapting messages and interface copy.
At iwoca, I used semi-structured interviews to inform a more consistent set of job descriptions. Other work has included automated checks, improving onboarding, and reading the legislation closely enough to unblock a launch.
The details that matter.
What was fun to improvise in a startup can become frustrating to maintain in a scaleup. I take a systems view: improving what people need today while making it easier to adapt tomorrow.
An 80% solution can be good enough to put to work. Getting to 90% is often much harder, but that is where something that works can become pleasant to use and easier to develop further.
I focus on that next stage, building on a useful first version someone else has delivered. My contribution is polish, finesse, and continuous improvement.
Companies accumulate documentation debt alongside technical debt. Missing explanations, outdated instructions, and decisions nobody has written down make further development harder. Putting the documentation in order can be a first step towards understanding and paying down the debt in the system itself, while keeping operations staff happy along the way.
He was great at acting as the bridge between the business & the cyber / tech domain.
Maximilian Heinemeyer
Chief Product Officer, Darktrace · 2022