Skip to content
Director-Tech
John Reinmann, President of Director-Tech Inc.

Bio

John Reinmann

Hired to own a company’s technology and to lead the people who run it, as a longer-term partner, then leave both the estate and the team able to continue without him.

President, Director-Tech Inc. · Northeast Ohio

John Reinmann is engaged to own a company’s technology and to lead the people who have to live with it, as a longer-term partner, then leave both the estate and the team able to continue without him. That has been the consistent shape of the work since 1987. The platforms have changed. The obligation has not.

The early years established systems depth under real operating pressure. At Tandy (1987–1989) the work was pre-sales systems engineering—live customer environments and machines that had to run once the sale was made. At Telxon (1989–1997) the role was lead systems engineer for the engineering department: not corporate IT. The estate had to stay up for people designing products, not for ticket queues. Unix platforms and engineering applications (Apollo, HP, Sun, SGI; Mentor Graphics, SDRC Master Series) illustrate the obligation. They are not the proof of the hire.

From 1997 the practice became independent. Under Area 51 Consulting, clients were trained until they no longer needed outside help. The same ownership model was applied across municipalities, industrial operators, closely held companies, and interim director seats. Take responsibility for the technology that mattered and for the people who would continue to operate it. Make it understandable. Leave.

A seventeen-year engagement with Ansell Healthcare / Microflex was the longest expression of the same ownership-and-transfer model, in global manufacturing. The close of that chapter followed the same standard as earlier work: a successor who could run the next cycle with the previous owner out of the room — including the team, not only certificates and identity registrations.

Director-Tech Inc. has been the independent practice since 2009. Interim director seats and closely held industrial operators sit alongside the longer manufacturing chapter. The method has remained consistent across company size, industry, and technology generation. Living maps over tribal knowledge. Clear ownership. Boundaries that protect the business. An explicit test of whether the next person can run the next cycle without the previous owner in the room. That is the work Director-Tech continues to offer.

Education includes Business Management & Finance at the University of Cincinnati, with additional study at the University of Akron and Carnegie Mellon.

Away from the work, the standing interest is air and space.

Director-Tech Inc. (director-tech.com) is the independent technology-direction practice of John Reinmann in Akron, Ohio. It is not Director Technology Partners of New York or DirecTech Connect.

Speak with the line, write contact-us@director-tech.com, or dial (330) 661-9295. Akron, Ohio.

Historical engagements

The platforms change. The obligation does not.

Direct employment from 1987. Then the independent practice — Area 51, then Director-Tech. The platforms change. The obligation does not.

  1. Director-Tech Inc.

    2009–present · Independent practice

    Independent practice. That manufacturing engagement was the longest expression of the same model, alongside interim director seats and closely held industrial operators. The work is to take ownership of the technology that matters and of the people who have to live with it, then leave a successor who can run the next cycle.

  2. Ansell Healthcare / Microflex

    Seventeen-year engagement · Global manufacturing

    Ownership-and-transfer in a global manufacturing estate. The close of the chapter is a successor who could run the next cycle with the previous owner out of the room — including the team, not only certificates and identity registrations.

  3. Area 51 Consulting

    1997–2009 · Greater Akron · owner

    Independent practice. The same ownership model applied across municipalities, industrial operators, closely held companies, and public-sector constraints. Clients were trained until they no longer needed outside help.

  4. Telxon

    1989–1997 · Akron · Engineering

    Lead systems engineer for the engineering department — not the head of corporate IT. The estate had to stay up for people designing products, not for ticket queues. Unix platforms and engineering applications illustrate the obligation, not exposure.

  5. Tandy

    1987–1989 · Pre-sales systems engineer

    Pre-sales systems engineering in Tandy’s computer organization. Live customer environments and machines that had to run once the sale was made. The start of the same obligation.

The line books the time.

Speak from the site or dial (330) 661-9295. Monday–Friday, 8:00 a.m.–5:00 p.m. Eastern.