Three things we’re being asked about right now: usability, cloud, and AI tools

Right now, three themes come up repeatedly: usability and design, cloud capability, and AI-assisted software development.

1) Usability: it shows up in the numbers immediately

For us, design and UX isn’t about “picking colors.” We talk about usability: how quickly a user reaches the goal, and how often they get stuck.

That’s why many customers’ first request is essentially:
“Show us where the service is getting in the way and what we should do about it.”

We usually do the work like this:

• an assessment of the current state (UI, user journeys, observations from data)
• a prioritized list of fixes and improvements
• user testing and iteration: change, measure, continue

AI helps especially with creating prototypes and trying out alternatives quickly. But results only improve when someone reviews things through the user’s eyes and makes decisions with clear rationale.

2) Cloud: a deployment platform, not a special feature

Cloud is no longer an add-on you bolt onto a project. It’s the default: the service needs to be set up, monitored, backed up, and updated in a controlled way.

Typically, we’re asked two things:

• can this be delivered as a SaaS service, or
• can this be delivered to the public cloud we’ve chosen—so that someone also keeps it running properly

The benefits of cloud are well known: scalability, availability, security mechanisms, and cost visibility. What really matters, though, is architecture: what to build, how to scope it, how to secure it, and how to operate it without constant manual work.

3) AI-assisted development: yes to speed, but also to judgment

AI tools are now part of a developer’s standard toolkit. They speed up especially repetitive work: code scaffolding, tests, documentation, and refactoring.

At the same time, an old truth becomes even more important: speed doesn’t help if you’re heading in the wrong direction. A good outcome still requires professional skill—architecture, security, quality assurance, and the ability to define the scope properly. Meaningful use of AI still demands a high level of competence from the developer: you still need to understand what each line of code does, and be able to verify and change it when needed.

When routine work gets faster, more becomes feasible with lower risk and cost. You can see it directly in the renewed demand for tailored software.

If these topics are relevant for you, let’s talk. Often even a short assessment clarifies what to do first—and what not to do.