Skip to main content
All CollectionsTechnical Tidbits
Can I see your product roadmap for the next year?
Can I see your product roadmap for the next year?

About how we plan, and how it works.

Alex Lemaire avatar
Written by Alex Lemaire
Updated over a week ago

We often field this question, and it comes in many forms.

  • "What's in development right now?" or,

  • "Can I see your product roadmap for the next year (or a few years even!)".

Short Roadmap Available

Before we delve deeper, we _do_ publish "what we are working on right now" at this link (https://ideas.lemonadelxp.com/tabs/2-planned). The features elected to this view are typically the product of feature sponsorship (clients paying for features we feel benefit the entire userbase) or aggregate signals received through Productboard (the submit-an-idea button in the administrative area).

You'll notice that the roadmap is very "short."

This is intentional.

At LemonadeLXP, we don't believe in sacrificing quality to meet artificial deadlines - an inescapable flaw of long-term roadmaps. Everyone accepts that innovation and development take time. What's more, market pressures usually require rapid pivoting. Where we agree that technological advances and intricate real-world considerations can spoil a plan, why make distant commitments that ignore that things will likely change?

Elastic Time for Collaboration Is Vital

Many questions commonly surface at the end of a sprint:

  • Is the planned feature delivering value?

  • Is it as good as it could be?

  • Can we reduce its maintenance footprint so that we can iterate more rapidly?

  • Do we need to work our way out of any echo chambers?

  • Should any technical debt be handled before we press it into the master release?

  • Would the feature or software benefit from a bit more discussion and innovation?

Innovation comes from collaboration, testing, learning, and experimentation. The usual fracture occurs within this last statement when you sprint against a manufactured deadline. Resource plans aren't as significant as trustworthy, tested software.

Therefore, we only discuss published features to give us the flexibility to dream and to react to technological advances. We'd be crushed to learn that you'd dreamed up an entire approach based on a planned release (or something you heard on the phone) that got pushed because of a required pivot.

TLDR;

The short version? We'll never promise or publish a long-term roadmap to keep our minds open and feedback radars on. We need to be able to re-evaluate our plans frequently; cementing ourselves with soon-to-be-old ideas would be detrimental.

We promise to continuously innovate and listen to client signals to make optimal decisions at every pause.

Check our roadmap link regularly, and don't hesitate to get in touch if you'd like to discuss sponsorship!


Did this answer your question?