My Week Time Budget: Difference between revisions
Jump to navigation
Jump to search
(Created page with "As we go into OSE 3.0, time allocation for the founder pivots to: *Focus on standards, protocols, infrastructures for going to scale *Externalizing all design knowhow *Doing some remaining design, but primarily schematizing it for AI assist *Video and social media work - with team assist *Largely automated newsletter, blog, and regular communications workflows *Construction duty only in so far as training others, and any remaining tasks that require full system intellige...") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=General= | |||
As we go into OSE 3.0, time allocation for the founder pivots to: | As we go into OSE 3.0, time allocation for the founder pivots to: | ||
*Focus on standards, protocols, infrastructures for going to scale | *Focus on standards, protocols, infrastructures for going to scale | ||
*Externalizing all design knowhow | *Externalizing all design knowhow | ||
*Doing some remaining design, | *Doing some remaining design, while primarily schematizing it for AI assist | ||
*Video and social media work - with team assist | *Video and social media work - with team assist | ||
*Largely automated newsletter, blog, and regular communications workflows | *Largely automated newsletter, blog, and regular communications workflows | ||
*Admin automation | |||
*Construction duty only in so far as training others, and any remaining tasks that require full system intelligence | *Construction duty only in so far as training others, and any remaining tasks that require full system intelligence | ||
*Workshop leadership only in so far as it results in training others | *Workshop leadership only in so far as it results in training others | ||
=Communications Workflow= | |||
*Design workflow around MJ Log for core directionality, weekly direction meeting, and place into weekly progress report (automation) and others | |||
*AI assist parses existing assets and reporting (add simple updating protocol for OSE activity to wiki) for ongoing storytelling. May include digest of email communications, books, etc. Must be a coherent perspective leveraging big picture world relevance. Some tech dev. Base this on big picture items from Book, Site development, Enterprise Dev, Programs Dev, IT Dev, Iconic CAD, recruiting, task breakdown. Create core ongoing categories relevant to current work. | |||
Latest revision as of 14:04, 13 April 2026
General
As we go into OSE 3.0, time allocation for the founder pivots to:
- Focus on standards, protocols, infrastructures for going to scale
- Externalizing all design knowhow
- Doing some remaining design, while primarily schematizing it for AI assist
- Video and social media work - with team assist
- Largely automated newsletter, blog, and regular communications workflows
- Admin automation
- Construction duty only in so far as training others, and any remaining tasks that require full system intelligence
- Workshop leadership only in so far as it results in training others
Communications Workflow
- Design workflow around MJ Log for core directionality, weekly direction meeting, and place into weekly progress report (automation) and others
- AI assist parses existing assets and reporting (add simple updating protocol for OSE activity to wiki) for ongoing storytelling. May include digest of email communications, books, etc. Must be a coherent perspective leveraging big picture world relevance. Some tech dev. Base this on big picture items from Book, Site development, Enterprise Dev, Programs Dev, IT Dev, Iconic CAD, recruiting, task breakdown. Create core ongoing categories relevant to current work.