1,440 karma · joined July 3, 2018
Work: https://nonducorduco.com
Where we go depends on the philosophy we apply, and there's way too little philosophy for what to do when AI upends your intellectual craft profession.
All businesses exist to serve a customer, and to help them achieve the outcomes they desire, so to the extent that you can apply these skills to those outcomes then you'll continue to be gainfully employed in a business context.
I think zero sum applications of software like internal tools with fixed scopes will rapidly be automated away with these tools. By comparison, positive sum product engineering of novel technologies seem like they are still hiring.
Would focus on bridging your technical skills into product engineering and deeply understanding a specific customer domain, invest in EQ through coaching and therapy and continue adopting AI tools to optimize your work.
The real purpose is an assessment of product/market fit, customer adoption, product development and financial results. Each are taken up qualitatively and qualitatively based on an artifact (either memo or slides) created by the CEO and discussed during the meeting.
The CEO creates the agenda, proposes it to the board members who give feedback, then creates the artifact based around the agenda in order of importance. Discussion ensues about the artifact and how much progress is being made, how satisfying that is, and changes/decisions for the CEO to take in follow-up.
It's typically a discussion meeting rather than a decision meeting. It should force reflection and progress with the CEO contriving and making decisions about changes to make to financial, customer and product decisions in follow-up solo. Then the next meeting you check on what effect that had.
(Canadian founder in unrelated domain)
Disclosure: worked at Shopify
1. Is the problem that you're going to solve important? Do people respond to cold email about a hypothesis to solve it? (testing problem relevance)
2. Is the solution that you put forward realistic sounding to customers? Do they believe that you'll be able to build it, and want it if you do? (testing solution relevance)
3. When you show customers an early version of what you're building, do they ask to use it (testing problem/product fit)
4. When early users get access to your sketchy prototype, do they usage retain? Regardless of funds changing hands, do they keep using it?
If you have a product where you can email people about a problem, who consistently reply, see a demo of your product and ask to use it, then adopt it and continue using it without pressure, you should figure out pricing.