Team Composition — Decision Criteria for Assigning Work to the Right People

This section reveals the structural causes behind project teams falling into dysfunction.

"We assembled talented people, so why isn't the project moving?" — this is a classic problem faced by directors in contract production work and freelance teams. Deadlines slip, quality is inconsistent, and communication costs run three times higher than expected. The cause is not the quality of the people. It is a design failure in team composition.

Team composition is not simply deciding who to bring in. It is designing a structure: who is responsible for what, who reports to whom, and who has authority to decide what. Without this structure, assembling people will always produce three predictable problems.

Role Overlap and Gaps

When roles are not clearly defined, the same task gets done independently by multiple people (overlap), or sits untouched by anyone (gap). In website production, a copywriter and a director each assume the other will write the text — so neither does. Or both write separate copy, and hours are spent negotiating which version to use. Both are representative examples.

Overlap and gaps are both costs. Overlap consumes labor twice. Gaps generate rework.

Decision-Making Stagnation

"Does this change need director approval, or can the designer handle it independently?" — when this kind of judgment is left ambiguous, team members freeze. Freelance members in particular tend to avoid overstepping, making them prone to waiting for instructions. In-house members, on the other hand, may act on their own initiative and trigger downstream changes.

In a team without a decision authority map, minor confirmations take hours — sometimes days.

Accumulated Mismatched Expectations

Many directors expect freelance members to "just know" what's needed because they're professionals. But in a freelance contract relationship, asking for work outside the scope of the agreement is structurally unreasonable — both formally and practically.

"They should understand without being told" and "they did it on the last project so they'll do it this time" — when these assumptions collapse, a team deteriorates rapidly.

This section presents three decision axes for structuring team composition decisions.

Relying on intuition or personal connections for team composition decisions will always produce distortions later. Establishing clear decision axes enables reproducible team design.

Axis 1: Skill Clarity

The first question to ask is whether the work to be assigned involves a clearly defined skill.

"Landing page coding (HTML/CSS/JavaScript)" is a clearly defined skill. The deliverable is concrete and quality criteria can be made relatively explicit. Work like this is well-suited for external specialists — freelancers or contractors.

By contrast, work like "design the user experience" or "develop a concept aligned with business strategy" has blurry skill boundaries and requires deep contextual understanding. Delegating this kind of work to external parties without ongoing context sharing almost always produces deliverables that miss the mark.

The lower the skill clarity of a task, the more it should be assigned to in-house resources or partners with established long-term trust relationships.

Axis 2: Need for Control

The second question is how much intervention is needed during the execution of the work.

Work that requires regular check-ins and course corrections should be assigned to roles where control is possible — in-house staff or people available for close, frequent communication. Conversely, work where the result itself is the check is lower in control requirements and suited to freelance contracts.

Assigning work to a contractor when you feel the need to communicate about it every day is a structural mismatch. It represents a practical demand for a direction-and-control relationship, which may raise issues under Japan's Freelance and Business Transactions Fair Treatment Act.

Axis 3: Risk Concentration

The third question is whether the project would stop if this person left.

Positions that could become a single point of failure (SPOF) should not be assigned to freelance members. Contract terminations, illness, and unexpected commitments to other projects — sudden departures are possible in freelance relationships. Concentrating core knowledge, decision authority, or client contact in a single freelance individual means the project bears that risk directly.

Core high-risk positions should be staffed by in-house members or long-term exclusive partner contracts.

This section organizes the appropriate conditions and caveats for freelance, employee, and partner arrangements.

When Freelance Works Best

Freelancers and external specialists perform best when all of the following conditions are met:

• Deliverables can be clearly defined: What constitutes completion can be specified in a contract or specification document
• The engagement is time-limited: Participation covers a specific phase or specific skill requirement
• The skill is specialized: Fills a gap not available in-house (video production, specific engineering language, etc.)
• Evaluation is deliverable-based: The result, not the process, is what is assessed

Conversely, freelance arrangements are difficult in these conditions:

• Project direction is still being established and frequent adjustment is required
• The role requires direct communication with clients or end customers
• The work fundamentally depends on high-frequency, close collaboration with in-house team members

When In-House Staffing Works Best

Work whose value grows from the accumulation of ongoing context should be handled by in-house resources. Brand understanding, organizational culture, and client relationships — even the most skilled external professional has limits to how much of this they can absorb in a short time.

Additionally, work that requires a direction-and-control relationship should rely on employment rather than contracting. Routinely instructing a freelancer to "arrive by 9 AM" or "prioritize this task" constitutes disguised employment — a legal compliance issue under Japanese labor law.

Using Partners (Ongoing External Collaborators)

Between full in-house staffing and one-off freelance contracts sits a third form: the ongoing partner. This refers to freelancers or external specialists whose repeated project-based engagements build a foundation of trust and shared context over time.

The primary advantage of partners is context continuity. There is no need to brief from scratch each time, and communication costs fall significantly. However, if dependence on a partner becomes too deep, the SPOF problem re-emerges. Parallel efforts to document knowledge and establish transfer mechanisms remain necessary.

This section presents a practical framework for preventing role overlap and gaps.

Structurally preventing "I said it / you didn't say it" and "I did it / no one did it" disputes requires explicit documentation of responsibility boundaries. The simplest and most effective tool for this is the RACI chart.

Using a RACI Chart

RACI is a framework for clarifying four roles for each piece of work:

• R (Responsible): The person who actually does the work
• A (Accountable): The person with final authority and decision-making power (one person only)
• C (Consulted): Those whose input should be sought before or during the work
• I (Informed): Those who should receive reports or updates on results

For the top-page design in a website redesign project, for example:

• R = Designer (production lead)
• A = Director (decision authority over direction)
• C = Client contact (brand guideline confirmation)
• I = Development engineer (informed for upcoming implementation)

Creating this table for each major task makes it immediately clear who can decide what and who needs to be consulted.

Handover Design and Preventing Knowledge Silos

No matter how capable the individual, a state where only they know something is an organizational risk. Specialized knowledge held by freelance members can simply disappear when the contract ends.

The foundation of handover design is structured documentation. Work logs, records of decision rationale, tools used, and access permissions — these should be organized regularly so the project does not depend on any single person.

Agreeing on documentation practices at the project start — where things are stored, how often they are updated, and what format to use — is the most effective way to prevent future confusion.

Communication Design

Design the frequency and format of communication in advance, tailored to the team's size and composition.

• Weekly standups: Progress review, blocker sharing, alignment on next week's priorities
• Asynchronous channels: Daily questions and updates (Slack, etc.)
• Decision records: Important choices are documented, not just verbally agreed (verbal-only decisions are prohibited)

When multiple freelance members are involved, channel design is also important. A structure where everyone receives all information creates decision fatigue. Design information flow intentionally based on each person's level of involvement.

This section covers signals that a team is heading toward dysfunction before it breaks, and the recovery steps to take after it does.

Catching Warning Signs Early

Teams do not collapse suddenly. There are always early signals. When several of the following appear together, there is a high probability of a structural problem.

Changes in communication frequency: Declining attendance at standups, slower chat responses, reports becoming shorter or less frequent. This indicates either rising disengagement or that team members have exhausted their buffer capacity.

Increases in "someone will handle it" statements: A typical reaction when role gaps exist. Deadlines approach while no one takes ownership.

Silent scope expansion: Work accumulates beyond the original scope without anyone explicitly agreeing to it. Freelancers extending themselves out of service orientation are building toward eventual resentment.

Increased escalation of minor decisions: When even small judgments require confirmation more frequently, decision authority has become unclear.

Recovery Steps

When breakdown signals appear, address them in the following order.

Step 1: Visualize the current state List what is stalled. Create a table of tasks, responsible parties, deadlines, and statuses. Identify gaps and overlaps. The starting point is understanding the facts without emotional assessment.

Step 2: Role redefinition meeting Gather all members (including freelancers) and use RACI to reconfirm current roles. In this session, explicitly identify tasks with no owner and areas of duplication, and reach new agreements.

Step 3: Reset communication rules Redesign the structure of standup meetings, asynchronous channels, and decision records, then communicate it to the team. Explaining the reasoning behind the rules drives higher adoption than announcing the rules alone.

Step 4: Scope audit Identify work that freelance members have been handling implicitly outside their contract scope. Decide whether to formally include it in the contract, set separate compensation, or remove it entirely. Leaving it unaddressed harms both parties.

Team composition is not a one-time design decision. Roles need to be revisited each time a project phase changes. Making that revision consistently is one of the core responsibilities of a director.

References

Basic Knowledge on Dispatched Workers, Subcontracting, and Outsourcing (2023)

Labor Statistics Time Series Data — Trends by Employment Type (2024)

Japan Institute for Labour Policy and Training (JILPT) (2024)