The best product conversations start with a problem. Whether that relates to timing, automation, complexity, or something that doesn’t exist, once the problem is identified, there is an opportunity to work in partnership to find a solution.

Problem solving is what I enjoy the most about working at the intersection of technology and education here at Wisenet. After more than 20 years across engineering, product, and technology, I’ve learned that building good software starts with curiosity. You need to understand what people are trying to achieve, why something isn’t working for them today, and then work out what you should change or improve to make a genuine difference.

Education feels like a natural fit because, at its heart, it’s about lifelong learning. It’s about developing new skills, challenging what you know, and staying open to new ideas. I think the same should be true of the technology that supports it. Wisenet needs to keep learning too: from our customers, from how education is changing, and from new possibilities in technology.

That means our job is to continually improve Wisenet around the real challenges education providers face, helping you manage complexity across learner administration, compliance, reporting, finance, communication, eLearning, and the workflows connecting it all.

Start with the problem, not the product

Wisenet customers aren’t spending their days thinking about software features. There are enrolments to process. Learners to keep engaged. Compliance requirements to meet, administration to reduce, and teams that have a lot to get through. That’s the context we need to understand before we decide what to build.

A big part of my role is understanding the problems behind the feedback and requests we receive, and deciding where we can create the most meaningful value.. Someone might tell us they need a particular feature, but there’s usually a bigger question behind it: what are they actually trying to achieve? Where is the friction today? How are they working around it? And is the same challenge affecting other providers? Those conversations help us distinguish between solving an individual request and solving a problem in a way that creates lasting value for many customers.

That curiosity also shapes how we think about new technology. AI is creating enormous possibilities, and I’m fascinated by where it might take us, but adopting technology for the sake of it isn’t the goal. The important question is where it can create genuine value: removing repetitive work, making information easier to use, or helping people make better decisions.

Partnerships work when built on outcomes

Whether it’s AI, automation or another new capability, I want us to start with the outcome we’re trying to achieve and work backwards from there.

That’s where partnership becomes really important. We know technology, we know Wisenet, but customers are the experts of their own organisations. They understand their learners, their teams, their processes, and their pressures.

We build better products when we bring those two perspectives together.

For me, partnership means being able to have an open conversation about what’s working, what isn’t, and what could be better. Sometimes there’s an opportunity to automate a process, connect another system, or make better use of functionality that already exists. And sometimes a customer challenges us to think about a problem in a completely different way. Those conversations are valuable because they help us look beyond what customers need from Wisenet today and consider what they might need from us next.

That’s also why I’m inspired by people who aren’t afraid to think differently. Education and technology are both changing quickly, and some of the most interesting ideas come from questioning the way something has always been done.

My advice to customers is simple: keep talking to us, and bring us the problem and the outcomes you wish to achieve. Tell us where your team is losing time, what’s becoming harder as you grow, and what you wish worked differently. The more we understand the context, the better we can work together.

Because, ultimately, that’s what a strong partnership should do. I want to create relationships where we continue to learn from each other and challenge assumptions. We won’t always have every answer immediately, but if we understand where our customers are trying to go, we can keep building Wisenet to help them get there.