Author: Dipak Patel, Client Innovation Director, Namos Solutions
Let’s be honest, the hardest part of continuous innovation isn’t finding out what’s new, it’s deciding what’s worth your time.
Because if you’re running your business on Oracle cloud applications, every quarter presents you with a lot of possibilities. And without a simple way to prioritise, most organisations fall into one of two traps.
The first is “new and shiny” adoption, you spot something interesting, switch it on (or start exploring it), but it doesn’t really land in the business. It’s not that it’s a bad idea… it’s just not connected to what matters most right now.
The second trap is the opposite: “defer it.” You postpone change because it feels safer, you’re busy, or you’re not sure you’ve got the capacity to absorb it. Again, totally understandable but over time defer becomes a habit (and bad one) and innovation debt starts to pile up.
Neither approach creates real impact.
So, here is a practical way to choose innovation in a way that feels connected, achievable, and gets adopted. Not a bureaucratic process, just clear decisions, shared ownership, and a roadmap the business can trust.
Your business pain is the filter not the feature list
I can recall as clear as day, a trip to the Nordics with my then CTO to meet with 2 high-tech firms that had just merged. We were there to review product ideation/design system related business challenges but the conversation leading up to the meeting showed all the warning signs it was about to spiral into details on features and benefits of new roadmap capabilities (having intelligent non-sequential or sequential non-intelligent part numbers was their hot topic).
He reframed the conversation with his opening 3 slides, each with just one sentence.
“Our technology is useless”
“Unless it changes your business”
“For the better”
They got so excited about the technology itself, the automated number generation and the whizzy new features that were coming that they’d lost focus; how to make the business better through the merger. After a short and slightly uncomfortable silence the meeting changed to something far more productive leading to the right decision, for the right reason.
So, if I could give you one thought to carry into every quarter, it’s this: Don’t start with the release notes but start with what hurts. What’s not working today and why? Where is there friction? Where are people compensating with spreadsheets, workarounds, or manual effort? Which goals are you struggling to achieve because of the process or lack of insight to support decision making?
Release notes matter, and I’m a big believer that continuous innovation from Oracle is brilliant. But the feature list in a quarterly update isn’t a strategy.
The best prioritisation conversations I’ve seen start with questions like:
- Where are we losing time every single week through inefficiency?
- Which business outcomes are we under pressure to deliver?
- Where do users avoid the system because it feels hard, slow, or unclear?
- What’s stopping better decisions? Is it data, reporting, forecasting, confidence?
Once you have clarity on that, adoption of new capabilities and innovation gets simpler. Because you’re no longer asking, “what should we adopt?” you’re asking, “What should we adopt to address something important?”
The simplest model usually works: Now / Next / Later
There’s enough complexity in what we all do so let’s keep this part simple.
A Now / Next / Later approach does two things; it helps you stay focused, and it stops innovation becoming either chaos or avoidance.
Here’s how I think about it.
Now is for the changes that are clearly relevant and realistically achievable and remove friction, reduce risk, or unlock value without major disruption. The kind of improvements where you can say: “we know why we’re doing this, we can do it safely, and the business will feel it.”
Next is for the things that matter but need a bit more preparation. Maybe there’s a process decision to make, or you need enablement/change management for it to stick. Maybe there’s data readiness, reporting foundations, or an integration dependency. It’s not “no” it’s “not yet, because we want it to land properly.”
And Later is the bucket that quietly saves your sanity. It stops you saying no to everything, while still protecting focus. It’s where good ideas live until the timing is right.
What I like about this is that it turns prioritisation into a shared conversation not a debate or a spreadsheet exercise.
Cloud Success Navigator is important, but rhythm matters more
Oracle Cloud Success Navigator (CSN) is a great tool to support adoption and at Namos we are proud advocates. It helps teams understand what’s changing, explore updates, and track progress. But here’s the nuance: tools don’t drive adoption, habits do.
The benefit of CSN multiplies when it becomes part of your operating rhythm. Not an “extra portal someone checks sometimes,” but a place where you capture decisions and maintain a visible roadmap.
Imagine using it as part of your QBR rhythm and aligning new capability to your priorities keeping a jointly owned kanban-style view of what’s Now, Next and Later. When you do that, “what’s new” becomes “what we’re doing next and why” and it stops being noise. At Namos we’re encouraging our clients to re-imagine their QBR’s and move to being forward-looking and outcomes based, not retrospective or dominated by SLAs and tickets. (system health is important, but that conversation is for the service review)
If you’re stuck choosing Now vs Next: ask these five questions
This is the simplest decision lens I’ve seen work repeatedly because it forces clarity without slowing you down:
- What problem does this solve? (described in plain English)
- Who benefits and how will they know it’s better? (and who else do we tell?)
- What’s the smallest version we can adopt to prove value?
- What are the prerequisites?
- How will we measure success?
Even if the measurement gets refined later, you’ll still need a definition of “better” up front.
The takeaway
If you can’t decide what to adopt and why you’re doing it, you won’t end up adopting anything that truly matters. Keep it simple and start with business pain using Now / Next / Later to protect focus. Make it collaborative keeping one visible roadmap and define success criteria early, even if the measurement matures over time.
Because in the end those that win using Oracle cloud applications aren’t the ones adopting the most features, they’re the ones adopting the right things, in a way their business can feel it, measure it, share it.
And that’s the perfect segway into Blog 3: once you’ve chosen what matters, the next question becomes: “How will we prove it made a difference?”
