Related Posts
Kind souls who successfully exited to Google,
Would you be kind enough to refer me to a role at Google!
Came across a role that's a good fit. Would ideally like to target it through a referral and not by applying through the career site.
Would also love to maybe take you for a meal or alike to thank you for it :) Google
Does Donald Trump have WAP
“Nine” off white x Nike
Hi Sharks,
Need your help with referral at Aon
Additional Posts in #OverheardAtWork
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Another CxO agrees saying:
The word Discovery appears like we are randomly digging at different places trying our luck to discover "gold"
"roadmapping, planning" seems more disciplined activities.
Excellently Accenture lol
I say use the term the people you are speaking to will understand best. No use sounding agile if the person you’re speaking to is waterfall.
Nothing really wrong with discovery. Sounds like the boss just wants everyone sounding new and hip. If you’re not making what you do sound fancier are you even working? Lol
I think the appropriate term is discovery waterfall :)
In innovation projects you actually do want to stumble upon something new and therefore discover, rather than plan something out based on knowledge you and all consulting peers already possess.
How can you roadmap something when the solution/business case isn’t clear?
The point of a discovery phase is to quantify the potential opportunity and establish a business case. Roadmapping begins once all of that is clear.
I suggest roadmap discovery. In this phase you discover what the roadmap should be:)
Yeah - I get what they are saying. Discovery not only sounds like you lack direction, but that you hope to stumble upon it. Roadmapping sounds more like you have an idea in place, just getting it laid out.
You can’t lay out what you don’t know :)
Okay sure
I have heard a couple of internal senior executives balk at the term discovery when the consulting firms use it. To them, discovery should be done during the sales cycle, on the consultants side. If it’s done after the contract is signed and the consultants are on site and being paid, someone screwed up.
There’s nothing wrong with using Discovery/Define/Design/Develop/Deploy methodology as long as it’s outlined at the beginning so people know what the hell you’re talking about
« Having a plan to back up assumptions », could be a phrasing that sounds less scary. Often Discovery/research has bad press because it is assumed it would consume a lot of time without producing enough « real » outcome.
Or if development process terms like roadmapping and planning are the ones that work, use « scoping » another very legit step in dev process. Research is definitely a part of scoping. No need to even use the word then.
Always go with the words and models that suit the decision makers.
In some previous consulting experience, we would also use the term Requirement Definition, sometimes in the context of a Discovery Phase, sometimes in of itself. But typically in the former, a Discovery phase would often include both “Requirement Definition” and “Research” activities. In that light, the Discovery phase would have both disciplined and generative elements to it, so to speak.
It used to be called Exploration
There’s 2 things: discovery mode and discovery.
The first is an illness, the second is a short period of time to get the requirements.
Here is what the lingo “discovery mode” really means and how to understand it, in plain words:
Discovery mode = unstructured
Discovery mode = you have no plan
Discovery mode = trial and error
Discovery mode = absence of leadership
Discovery mode = costs more
Discovery mode = inability to define a strategy
Discovery mode = internal kindergarten
Discovery mode = lack of discipline
Discovery mode = are you lost?
Discovery mode = have you analyzed it?
Discovery mode = a internal thing to say we don’t know what to do but we try not to appear fully incompetent
Discovery mode = same as previous but replace what to do by how to do it
Discovery mode = are you a Dora?
Discovery mode = is it fundamental research?
Discovery mode = do you need emergence or exploration? If not that’s irrelevant.
Discovery mode = lack of experience
Discovery mode = lack of expertise
Discovery mode = inability to set a vision
Discovery mode = inability to define high level requirements
Discovery mode = absolute screw up dissimulated
Discovery mode = we don’t own it
Discovery mode = and we don’t care about it.
Discovery mode = no scope defined
The only acceptable meanings for Discovery (not discovery mode):
1- preproject business analysis aka Research aka High Level Requirements Definition (so limited in a timeframe)
2- project scoping (same as above)
3- continuous R&D