2,580 karma · joined October 20, 2011
Biz Dev at Everlaw
Formerly
Biz Dev at Pivotal>VMware>Broadcom
Product Manager at Capital One
Biz Dev at Viget (viget.com)
t: rhapsaadic
When I'm trying to closing six, seven, or eight figure software dev deals, this process definitely involves a "sales" type of person as well as two - three devs and architects.
The outcome is a proposal that sometimes is just a powerpoint deck with a summary of our understanding of the problem and the process / cost / timeline we'll take to solve it.
Once I deliver the proposal, then it's all about getting to agreement on cost, timeline, and then getting signed contracts. Rule number 1 is that a deal is never ever a deal until the contract is signed and executed.
Yes, the $1.4 Trillion is an all-in capitalized cost for the cost of the program, but the click-baity article gets to the heart of the issue pretty quickly: that building a product for 3 different users / businesses that each have their own unique needs and requirements is a failure of a product development strategy. You can either throw money at the problem and attempt to fix the product, or come to the conclusion that it's unfixable, admit that you were wrong, come up with a better product strategy and roadmap, and start all over again.
2 - Estimated Church Goers - https://churchleaders.com/pastors/pastor-articles/139575-7-s...
3 - US Population -- http://www.worldometers.info/world-population/us-population/
https://www.theguardian.com/commentisfree/2012/sep/25/study-...
> "Most of the 116 videos I watched generated very few views. The average video had less than 10 views, although a handful had more than that."
[1] - https://support.google.com/analytics/answer/6366371?hl=en
Now that I'm settled into my new job, it's the one thing that I'm still doing more regularly than going to the gym or going on hikes.
"Cool clock, Ahmed. Want to bring it to the White House? We should inspire more kids like you to like science. It's what makes America great."
[1] - http://www.bizjournals.com/southflorida/print-edition/2015/0...
edit - grammar
The plan then turns into "I'll test once it's live, once I have actual usage data". But, testing never occurs, and instead, your product team is faced with scope creep. You (or your stakeholders) think that a product is failing because you haven't jammed enough into it already, so go ahead and jam more features into it. Build all the things!
The cycle then repeats until the product is pronounced dead. sometimes on arrival, sometimes many months or years later.
So, the sooner product creators, designers, and developers let go of the fear of testing, the sooner a team can arrive at a product market fit.