Behind the builder / 19 July 2026
Everything cannot be the flagship
Games, tools, and an AI company all compete for attention. Inside the UBIKITOS effort to organise a creative portfolio without making every project priority one.
The portfolio needed an order
The work on 19 July was portfolio structure and governance preparation. The problem was not a shortage of possible projects. Too many company and project surfaces were competing for attention at the same time.
The next step was to create a hierarchy and stop treating every direction as equally urgent.
That is a deceptively simple instruction. In a creative portfolio, the projects can all have plausible reasons to matter. One offers a commercial possibility. Another develops a useful capability. A third is personally interesting and might eventually connect to the others.
The difficulty is that “worth keeping” and “worth doing now” are different decisions. If they are treated as the same decision, the active queue becomes a catalogue of everything the founder does not want to lose.
Today was about making that distinction clearer. The portfolio needed a way to preserve its possibilities without asking each possibility to become the main assignment at once.
Equal priority is a hidden decision
Calling several projects equal priorities can feel fair. It avoids making an uncomfortable choice and acknowledges the potential in each direction.
In practice, the choice still happens. It is made by whichever task is easiest to start, whichever conversation is most recent, or whichever problem interrupts the day most loudly.
That is a poor substitute for an explicit order. A project can receive attention because it is accessible rather than because it advances the most important dependency.
A hypothetical portfolio makes the issue visible. Suppose one project needs a missing technical foundation, another needs customer discovery, and a third is ready for a small delivery. Giving them identical priority does not tell the founder how to spend the next hour. Their needs are different, and some work may unlock several others.
The 19 July task was to create a hierarchy that could support those choices. It did not require pretending only one idea was valuable. It required deciding which relationship among the ideas should govern the next action.
A parked idea still has a place
One reason portfolios become crowded is that postponement can feel like abandonment. If an idea is removed from the active list, it may seem as though it has been judged worthless.
A better structure can preserve the idea and its context while making its inactive status clear. The record can explain what made it interesting, what remains uncertain and what condition would justify returning to it.
That is useful for a founder working with AI because the assistant may otherwise rediscover and reactivate old directions simply because they appear in the available context. A parked idea needs a status, not just a folder.
The point is not to create an elaborate bureaucracy around every possibility. It is to prevent the same prioritisation decision from being reopened accidentally in every new session.
Today’s governance preparation was aimed at making the portfolio more coherent. A good result would allow the project to remember its possibilities without continuously treating them as current instructions.
Shared foundations can help and distract
Projects in a portfolio may genuinely share useful infrastructure. A research process, a knowledge base or an execution mechanism can support more than one line of work.
That creates an opportunity to invest in something reusable. It also creates a tempting justification for endless foundation work: every improvement can be described as helping everything eventually.
The useful question is which concrete project needs the foundation next and what evidence would show that it helped. Reuse becomes meaningful when a real workflow can rely on the capability, not merely when several future plans mention it.
A hypothetical shared research tool might be valuable across the portfolio. But if no current project can complete its research task through that tool, the claim of reuse remains ahead of the evidence.
The portfolio hierarchy needed to make these dependencies visible. It should help distinguish a foundation that unlocks active work from a speculative platform feature that could theoretically serve many things later.
The founder is a limited resource too
Portfolio plans often count project tasks more carefully than they count the attention required to coordinate them.
Every active project carries context. Its current goal, its unresolved questions, its files and its decisions need to be understood before useful work resumes. Switching among several directions can create a substantial burden even when the individual tasks are small.
There is no measured time-allocation study in the 19 July record, so no savings percentage belongs here. The practical issue is clear without one: equal-priority thinking makes the founder responsible for repeatedly deciding which context to reopen.
A hierarchy can reduce that repeated decision. It can establish which project leads, which supports it and which waits for a specific dependency or external signal.
That is part of building a system intended to return human time. The operating structure should help the person preserve attention, rather than turning every new possibility into another open conversation they must manage.
A portfolio is not a collection of unrelated promises
When several projects sit beneath one company, it becomes important to explain their relationship without claiming they are all equally mature.
One may be a prototype. Another may be a research direction. Another may be a service concept that still needs market validation. Putting them under the same identity does not make their evidence interchangeable.
A clear portfolio structure can preserve those differences while showing the common purpose. It helps the founder decide where work belongs and helps a future reader understand what the company is actually pursuing.
The 19 July work was preparation for that clarity. It did not establish that every project had a working commercial model or a complete technical implementation.
Looking back, this is a useful reason to resist a portfolio presentation that makes everything look equally finished. A coherent company can contain experiments. The important part is to make their status understandable rather than letting the shared brand imply more than the individual records support.
The next decision needed to be easier
The day’s next action was to establish a hierarchy and reduce equal-priority thinking. The useful outcome would be a simpler answer to the question: what should happen next, and why this before the other things?
That answer should be grounded in the portfolio’s purpose and dependencies. It should be clear enough that the next working session does not begin by renegotiating the entire company.
There was still external validation to obtain and operating proof to build. Organising the portfolio did not remove those tasks. It could help put them in a more productive order.
For the diary, the central point is that keeping an idea alive does not require keeping it active. A founder needs somewhere to preserve possibilities and a separate way to choose the work of the day.
Everything can remain interesting. Everything cannot remain the flagship.