The decision before the delivery
Most conversations about external development begin too late. A team has work to place, a schedule to protect, or a capability gap to close. The immediate questions become familiar: Who can do it? How quickly can they start? What will it cost?
Those questions matter, but they assume the work is already ready to cross an organizational boundary. Often it is not. The desired outcome may be clear while the decision rights, review capacity, technical dependencies, acceptance standards, and escalation paths remain unresolved. A partner can inherit the assignment without inheriting the context required to make sound decisions.
The first external-development decision is therefore not which company receives the work. It is whether the operating system around the work is ready to support shared execution.
A handoff is never only a handoff
Creative production depends on judgment. Even a detailed brief cannot contain every tradeoff, historical constraint, audience expectation, technical risk, or creative intention. When work moves between organizations, teams are also transferring the conditions under which judgment will be exercised.
If those conditions are weak, the predictable symptoms appear later: repeated feedback, defensive documentation, slow approvals, late integration, avoidable rework, and disagreement about what “done” was supposed to mean. These are often described as partner-performance problems. Some are. Others began inside the commissioning organization before the partner entered the system.
Three questions before partner selection
- What decision is the organization actually making? Buying defined capacity, integrating specialist capability, sharing an uncertain creative problem, and building a durable strategic relationship are different decisions. Each requires a different level of context, governance, and mutual accountability.
- What must travel with the work? Leaders should identify the creative intent, technical constraints, dependencies, references, decision history, definitions of ready and done, review ownership, and risk language that a partner will need. If critical context can exist only in one leader's head or one internal meeting, the interface is not ready.
- What must remain owned internally? External development can extend capability; it cannot remove the need for accountable internal decisions. Creative direction, product priorities, integration readiness, timely review, and escalation authority need named owners with enough capacity to act.
Readiness is a leadership responsibility
A credible readiness review is not an attempt to eliminate uncertainty. Creative work will change. The purpose is to make uncertainty governable: to identify which decisions are settled, which remain open, who can resolve them, how quickly feedback can move, and what evidence will show that the model is working.
This also creates a fairer basis for evaluating partners. Without a clear operating interface, leaders may compare vendors on price, portfolio, and promised capacity while overlooking the conditions that will determine performance. With that interface defined, the conversation can move toward fit: communication behavior, technical compatibility, production leadership, cultural fluency, learning cadence, and the ability to surface risk early.
The series ahead
This prelude begins a broader Harvik series on the future of external development. The series will examine readiness, partner architecture, governance, cross-cultural operations, shared accountability, and the shift from transactional handoffs toward more integrated models of creative production.
The argument will build in sequence. It begins here because the strongest partnership cannot compensate indefinitely for a system that was never prepared to share the work. Before leaders debate the future model, they should examine the boundary they are asking people, decisions, and creative intent to cross.