Harnessing Technology Responsibly

Ken Judy
Ken Judy
Originally: Aug 8, 2024 | Enhanced: Oct 28, 2025
2 min read
Technology technologyinnovationleadership

Harnessing Technology Responsibly

2 Technology Post technology, innovation, leadership Aug 8, 2024 1723161600000

When applying new and expensive technology to a real world challenge. Understand the strengths, risks, and weaknesses of the tools.

Spend the time to understand how human experts solve the problem. Learn from them where tooling can improve the result: remove drudgery, spark human creativity, improve consistency. Design the interaction so the human remains in control and accountable for the output.

Apply existing tools to address solved problems and apply the novel tooling to address gaps. Work to achieve as replicable and useful a result as you can as efficiently as you can. These are the constrains that free an engineer to invent.

The result is a more responsible use of the tools. Respectful of people, careful with resources, mindful of impact.

Originally published on LinkedIn on Aug 8, 2024. Enhanced for this site with expanded insights and additional resources.

← Back to Articles and Posts

Related Content

innovation emblem

Harnessing Technology for Real-World Challenges

When I apply new and expensive technology to real-world challenges, I focus on understanding the strengths and weaknesses of these tools. I learn from human experts to see how technology can enhance creativity and consistency while keeping humans in control. By applying existing tools to known problems and using novel solutions for gaps, I strive for responsible and efficient outcomes that respect people and resources.

Technology technologyinnovation
2 min read Read Full Post →
innovation emblem

The Art of App Rewriting

There’s an art to rewriting an app without halting to do a “rewrite project”. A messy, tactile art. Like finger paints.

Technology app developmentinnovation
1 min read
leadership emblem

Defining Success in Tech Leadership

Dear tech executive, If you don’t know what you want or can’t articulate it coherently then speed isn’t your problem. Assuming AI code generation solves your problem is dead wrong.

“My engineering team consistently delivers the wrong thing.”

That’s a failure of definition, not implementation. Leadership either doesn’t understand the opportunity well enough to communicate it, or there isn’t one to begin with.

“Fail fast, learn cheap” works if you have something to learn from the experiments. If you can’t clearly articulate what you want, you won’t extract useful lessons from what gets built. Just building the wrong things faster isn’t the cure for that disease.

Leadership leadershiptechnology
1 min read