Digital Experience Labs

NO-CODE KNOW-HOW: Key 8 - Be Prepared to POC

The proof, as they say, is in the pudding. Be armed with a sample process or requirement and ask for a Proof of Concept (POC) that:

Focuses on areas where you have identified concerns/doubts;
- Allows for a detailed walkthrough of
- how it was built,
- how it runs,
- what skill level was required to build it and how long it would take for someone new to get there.
- Can be handed over to you to pick apart – this is where vendors get nervous if the POCs are held together by sticky tape.

Access to a trial environment with sample solutions or patterns is also a great way to get a real feel for how things work. Even better, get a POC and ask for it to be loaded into your trial environment so you can play with it yourself.

NO-CODE KNOW-HOW: Key 7 - Look Past the Smoke and Mirrors

Ready-made demos should look fantastic, after all, they’re designed to get you salivating over what may be possible. Go to any big product expo or conference and you’ll walk out with a bag full of hopes and dreams, but when the afterglow fades, you’ll need to delve into the detail about what’s needed to make those scenarios a reality.

Why is this important?

No matter which platform you choose, though, the chances are it won’t be long before you start thinking about more advanced functions.

By tapping into the Help function and some active Googling, you can work your way into more complex logic, but may hit a roadblock when you start getting into some of the more ‘interesting’ capabilities. They’re there, but they are harder to access, difficult to learn and hard to master. That’s when you realise that unless you commit to learning a new trade or hiring, you’ll need to look at other options or refocus on your goals, and keep things simple.

Understanding what it really takes to deliver an outcome is worthy of deeper analysis.

https://dxlabs.com.au/thoughts/no-code-know-how-9-key-considerations-before-choosing-your-platform/

NO-CODE KNOW-HOW: Key 3 - Consider Your Capabilities.

Why is this important?

It’s important to be clear about how technical you want your no/low-code designers/developers to be… Getting this wrong means you may end up needing to invest in skills you hadn’t budgeted for, build long-term partner relationships you didn’t want, or in the worst-case scenario, wind up with an unfinished or underwhelming solution. Of course, it doesn’t have to be that way.

Asking the right questions before investing and perhaps even more importantly, testing the platform will help you reach a sound understanding of where the no-code road ends and what skillsets you’ll need to deliver the outcomes you want or need.