2 cents to this thread, I made a simple demo of a sidebar using openai to support actual interactions with the 'browser stuff', not the web. Of course, it's not the case of agentic (if async this then async that) yet nevertheless I prompt us to think about that 'middle space' which actually values the browser functions. https://www.youtube.com/watch?v=qloYFzCwJu0
Location: GMT-8 to GMT-3 to GMT+2, from Brazil.
Remote: Yes, travel ok
Willing to relocate: Consider
Technologies: HTML5, CSS3, JavaScript, React, NodeJS, Docker; UX/UI Design, Technical Writing, Start-up Experience, Product Design Experience
Résumé/CV: https://www.mgalli.com/techwriter
Email: mgalli@mgalli.com
I am Marc S Galli, an evangelist, technical writer, and web producer. I am interested in helping build products for users. I started my career working for a browser vendor, under marketing, creating DHTML demonstrations, technotes, and helping with the product. I have experience with open-source development and tools, start-up experience and product design experience. I came from the world of prototypes but ultimately enjoy being a builder. A builder, through writing, as writing helps me to collaborate and build better things. Check https://mgalli.com/
I agree. That so far the super specialist can do better. But they will also find useful when they need to cross the domain that are good at with something that they are yet a beginner. Also, for mechanical things, it is amazing. Like, for helping solving a conflict of a patch with a context, or editing lots of parts in a code with something that it would require multiple regexps.
Entrepreneur-founder with technical skills in modern JS technologies. Although I have worked with core engineers, such as the inventor of JavaScript and browser developers; I never worked as a core engineer but always under marketing. Consider myself a JS protyper, UX-UI developer; but one that have a wider view of what happens with servers, client and HTTP networking.
Check this point of view based on writings and what I do. First, examples of front-end with UX and UI work:
Back-end for this project? Yes, Docker, NodeJS. But keep in mind that it is an MVP. Therefore, from the procuct perspective, it lives to test hypothesis and not with the goal of scaling.
Inspired by * I will elaborate a bit on what I think would be an OKR-approach for that. It could be a goal like "How am I supposed to know why customers are churning?". Then your key results would be, not the metric that says "Working on that", but the metric that helps you with answering the question in a way that proves or solves the puzzle ideally. There are many things that are solvable and for these the OKR recommends "Committed OKRs" while for things that are unclear there is the "aspirational OKRs".
Say, for the above: KR A being test the hypothesis for churning using XYZ analysis method and KR B bring peer review that with specialist named Klopvital, Tartirius and Mochalatet. Then, once you improved an answer, I would think you have achieved a partial goal - and if that is data to someone else then it comes the choreography of things.
. . .
The whole reason of a system of goals is to have one work and what OKR helps relates to accountability - what is a measure that validates the goal. Of course, the complexity comes when one goal system is chained with the other - the orchestration.
Your case "Someone needs to do the research, analysis, and leg work of finding potential areas to exploit." partially opens the door to it for the idea of Committed OKR (the kind of OKRs that one can do, solvable).
On your point "And then someone needs to have at least some amount of vision or inspiration about how to solve that problem." this seems to be about the idea of Aspirational OKR. In this regard, I agree that many things in the entrepreneurial outset starts with a north and not a precise thing. Certainly OKR is not a system to work on requirements - do it and that is that. The OKR approach is influenced by short feedback reviews for goals — that is derived or inspired by Andy Grove insights about MBO vs feedback vs planning that goes on like a) point to a roadmap b) work on it with a temporary plan in an accountable transparent way c) review the plan and review the roadmap.
But I hear your strong statement that "but the last time I worked in an environment with OKR no one seemed to have any brilliant ideas about how to, you know, actually achieve the Key Results." and would love to talk with you to understand more your experience. From the book I read I came upon cases that some of the success cases too years to fix their OKR system.
* Some of the ideas here I was inspired by the Measure What Matters book by John Doerr. But of course it's my limited interpretation.
