Amy, this is a good way to describe where this kind of work gets stuck.
One thing I’ve seen though - even when you get that working group and some pull, it still slows down if the underlying systems can’t take it in.
A lot of these solution packages look usable on the surface, but once they hit real workflows (catalog, pricing, legacy stuff), the friction shows up again.
so it’s not just getting people to engage, but also whether the system underneath is ready for it.
For me it’s usually been taking one small use case and forcing it into a real workflow early.
something like getting a sales or ops person to actually use it for a few days. that’s where things start breaking - data not lining up, edge cases, stuff not fitting how they actually work.
Most of the time the tool is fine but it is everything around it that slows it down.
so I try to hit that stage early instead of building more around the demo.
Amy, this is a good way to describe where this kind of work gets stuck.
One thing I’ve seen though - even when you get that working group and some pull, it still slows down if the underlying systems can’t take it in.
A lot of these solution packages look usable on the surface, but once they hit real workflows (catalog, pricing, legacy stuff), the friction shows up again.
so it’s not just getting people to engage, but also whether the system underneath is ready for it.
I’m planning to vibe code some tools and a dashboard once I get some traction.
What have you done to get past the next obstacles?
For me it’s usually been taking one small use case and forcing it into a real workflow early.
something like getting a sales or ops person to actually use it for a few days. that’s where things start breaking - data not lining up, edge cases, stuff not fitting how they actually work.
Most of the time the tool is fine but it is everything around it that slows it down.
so I try to hit that stage early instead of building more around the demo.
Thank you! This is a good next step.