Expected value is a wonderful topic. Easy enough to learn in an hour, but complex and applicable enough to keep you interested for years.
As someone who’s always in search of the answer, always trying to synthesize (or let’s be honest, over analyze!) a dataset into meaning, EV has become my sliderule, toolbox, and IDE, letting me input the right parameters to spit out an objective solution.
What if, as a Business Analyst, your approach to managing requirements could also apply to managing people? That’s an interesting proposition, right?
If you already have BA skills this makes the transition into a team leadership role easy. And as we’ll see, this management style is also well-suited to get the most out of the young knowledge workers filling up the modern entrepreneurial organization.
Within the technology industry there’s still a spectrum between marketing and engineering companies. Where does your company lie? It’s an important question to know. The answer impacts nearly all facets of how you operate.
Deep down, are you a marketing company? Does your company calculate its brand value and aspire to top this list someday?
Or are you an engineering company? It might be obvious, like the team over at Boston Dynamics:
Prototypes are great to quickly build out a representation of your ‘amazing’ new product idea. In the mobile app world prototypes are especially awesome because you have them at your disposal to share, promote and test wherever you are.
5 Reasons to Build a Prototype
This section will be short and to the point. Here we go: