Mapping Career Workflows: Process vs. Lattice

Most career development advice treats professional growth as a linear ladder—climb rungs, reach the top. But real careers rarely follow that script. This guide maps two competing workflow models: the traditional career process (structured, sequential, predictable) and the career lattice (flexible, lateral, adaptive). We explain how each model works in practice, where they break down, and how to decide which fits your organization—or your own trajectory.

Field Context: Where These Models Show Up in Real Work

Career process and lattice models are not abstract theories—they emerge from everyday decisions about hiring, promotion, role design, and skill development. In a typical engineering organization, for example, the career process manifests as a defined hierarchy: junior, mid, senior, staff, principal. Each level has explicit criteria, expected time in role, and a promotion review cycle. The lattice, by contrast, might appear as a rotation program, cross-functional project assignments, or a dual-track system where an individual contributor can grow in influence without managing people.

We see process-dominant workflows in large, regulated industries: government, healthcare, finance. These environments value predictability, equity, and defensible decisions. A promotion process with clear rubrics reduces bias and legal risk. But it can also create bottlenecks—people wait for slots to open, or they stagnate if they don't fit the mold. Lattice-dominant workflows show up in startups, consulting firms, and creative agencies. Roles are fluid, titles matter less, and growth means expanding scope rather than moving up a list. The trade-off is ambiguity: without clear criteria, advancement can feel arbitrary, and employees may struggle to articulate their value.

Consider a composite scenario: a mid-sized product company with 200 engineers. They use a process model: four levels, annual reviews, a promotion committee. It works for a while, but after a hiring spree, the pipeline clogs. Senior engineers leave because they see no path to staff. The company experiments with a lattice—introducing tech lead rotations, mentoring tracks, and project-based title adjustments. Some thrive; others feel lost without a ladder. The lesson: the right model depends on team size, culture, and the kind of work being done. Neither is inherently superior.

Where You'll Encounter Each Model

Process models dominate in environments where consistency and compliance matter—think payroll systems, audit trails, and union agreements. Lattice models thrive where innovation and adaptability are paramount—research labs, product design, cross-functional squads. Most organizations, however, operate in a hybrid space. The question is not which one to pick, but how to map the workflow to the work.

Foundations Readers Confuse

The most common confusion is equating the career process with a promotion process. A promotion process is part of a career process, but the latter encompasses how work is assigned, how skills are developed, and how people move across roles—not just upward. Similarly, a lattice is not the absence of structure; it's a different structure based on nodes and connections rather than rungs.

Another misconception: that a lattice is always more flexible. In practice, a poorly designed lattice can be as rigid as a process—if every lateral move requires sign-offs from three committees, the lattice becomes a maze. Conversely, a well-designed process can be adaptive if it allows for exceptions and fast-track approvals. The key is not the label but the underlying rules: who decides, how often, and what criteria are used.

We also see confusion around equity. Process advocates argue that clear criteria reduce bias; lattice advocates argue that multiple paths increase opportunity. Both can be true, but only if the system is transparent. A process with opaque criteria (e.g., “leadership potential” undefined) still invites bias. A lattice with invisible gatekeepers (e.g., only certain projects count as “stretch”) can exclude the same groups it intends to help.

Common Definitional Traps

People often treat “career path” as synonymous with “promotion track.” A career path includes lateral moves, role changes, and skill acquisition. A promotion track is just one vector. Similarly, “career lattice” is sometimes used to mean any non-linear career, but in workflow terms, it refers to a specific design: a graph of possible moves, each with prerequisites and outcomes. Without that structure, it's just chaos.

Patterns That Usually Work

In process-dominant organizations, the pattern that works best is the aligned rubric. Each level has a small number of concrete, observable behaviors—not vague adjectives. For example, “independently completes features of moderate complexity” is better than “strong problem-solving skills.” The rubric should be co-created with current role holders, not dictated by HR alone. When people understand the rules, they can play the game fairly.

In lattice-dominant organizations, the pattern that works is the portfolio approach. Employees build a portfolio of experiences: a stretch project, a mentoring assignment, a cross-team collaboration. Advancement is based on the breadth and depth of the portfolio, not time served. This requires managers to actively curate opportunities and employees to document their work. A simple portfolio template (project name, skills used, outcomes, reflection) can make the lattice tangible.

A third pattern, useful in hybrids, is the career corridor. Instead of a single ladder or a full lattice, define a few broad corridors (e.g., technical depth, people leadership, product strategy). Within each corridor, there are levels (process), but people can switch corridors (lattice). This balances structure with flexibility. Companies like Spotify and Microsoft have experimented with corridor models, though the details vary.

Implementation Tips

Start with a pilot team. Pick a group that is open to experimentation and has a clear need (e.g., high turnover in a specific role). Design the workflow with their input, run it for six months, and measure engagement, retention, and perceived fairness. Use the results to refine before rolling out broadly. Avoid the temptation to design the perfect system upfront—it will be wrong.

Anti-Patterns and Why Teams Revert

The most common anti-pattern is the false choice. Teams decide they must be either process or lattice, then force-fit everything into one model. A sales organization might adopt a rigid process (quotas, tiers, promotions) that ignores the value of cross-territory learning. A design team might embrace a pure lattice (no levels, everyone a “senior”) that leaves junior designers without guidance. Both extremes fail because they ignore the nature of the work.

Another anti-pattern is the ladder illusion. An organization claims to have a lattice but still only rewards upward moves. Lateral moves are seen as “sideways” or “demotions.” This happens when culture hasn't caught up with structure. People quickly learn that the real game is the ladder, and the lattice becomes a dead letter. Fixing this requires changing what gets celebrated—publicly recognizing a successful lateral move or a role expansion as much as a promotion.

Teams also revert when the system becomes too complex. A lattice with dozens of possible moves and prerequisites becomes unmanageable. Managers can't advise employees, and employees can't plan. The system collapses back to a simple ladder because that's what people can understand. The antidote is to keep the number of moves small and the criteria clear. If you can't explain a move in two sentences, it's too complex.

Why Reversion Happens

Reversion is often driven by leadership turnover. A new VP brings a “proven” process from their previous company, ignoring the context. Or a founder who loved the lattice leaves, and the board demands more structure. The best defense is to document the rationale for the current model—what problems it solves, what trade-offs it accepts—so that new leaders can evaluate before changing.

Maintenance, Drift, or Long-Term Costs

Both models require ongoing maintenance. For a process model, the cost is keeping rubrics current. As roles evolve, criteria become outdated. A rubric from 2021 might not reflect the skills needed in 2025. Review and update rubrics annually with input from people in those roles. The cost of not updating is misalignment: people are evaluated on obsolete criteria, leading to frustration and attrition.

For a lattice model, the cost is opportunity curation. A lattice only works if there are enough meaningful moves available. If the organization is flat or shrinking, the lattice becomes a map of closed doors. Leaders must actively create opportunities—temporary assignments, cross-team projects, mentorship roles. This takes time and budget. Without it, the lattice becomes a source of disappointment rather than growth.

Drift is another risk. Over time, informal norms replace formal rules. In a process model, managers might start making exceptions for favored employees, undermining equity. In a lattice model, a clique might control access to the best projects, creating a shadow hierarchy. Regular audits—anonymous surveys, promotion data analysis, exit interview themes—can detect drift early. The cost of ignoring drift is loss of trust, which is hard to rebuild.

Long-Term Cost Comparison

Process models tend to have higher upfront design costs (writing rubrics, training managers) but lower ongoing coordination costs. Lattice models have lower upfront costs (you can start with a whiteboard) but higher ongoing costs (managing opportunities, tracking moves). Neither is cheaper overall; they just shift where the investment goes.

When Not to Use This Approach

Do not use a process model when the work is highly novel and unpredictable. If every project is different, fixed criteria will miss the point. A research lab exploring new technologies should not be constrained by a promotion rubric that rewards predictable outputs. Similarly, do not use a lattice model when the work is tightly regulated and requires clear accountability. A hospital cannot have nurses “rotating” into surgery without certification—the lattice would violate safety standards.

Do not use a process model when the organization is too small to sustain levels. A startup with ten people does not need a five-level hierarchy; it creates artificial distinctions and slows decision-making. A simple “junior/senior” split or no levels at all may work better. Conversely, do not use a lattice model when the organization is too large to manage informal moves. A company of 10,000 cannot rely on word-of-mouth for opportunities; it needs a system to make them visible and fair.

Also avoid using either model as a substitute for good management. No workflow can fix a manager who doesn't coach, give feedback, or advocate for their team. The model is a tool, not a replacement for leadership. If the underlying culture is toxic, no amount of process or lattice design will help.

Signs You Might Be Using the Wrong Model

If employees complain that promotions are arbitrary, you might need more process (clearer criteria) or better lattice (more paths). If they complain that they feel stuck, you might need more lattice (lateral options) or better process (faster reviews). The key is to listen to the specific complaint and diagnose the model mismatch, not just switch to the other extreme.

Open Questions / FAQ

Can we combine process and lattice in the same organization?

Yes, and most successful organizations do. The trick is to decide which parts of the career workflow follow a process (e.g., base pay bands, promotion minimum criteria) and which follow a lattice (e.g., project assignments, skill development). The hybrid must be coherent: employees should understand when they are in process mode and when they are in lattice mode.

How do we measure if our model is working?

Track three metrics: internal mobility rate (percentage of moves that are lateral vs. upward), time to promotion (or time to meaningful growth), and employee perception of fairness (via anonymous survey). If mobility is low and fairness scores are declining, the model needs adjustment.

What if our industry standard is a ladder, but we want a lattice?

You can still experiment within a team or department. Use a different title structure internally (e.g., “tech lead” instead of “senior engineer”), but map to external titles for recruiting. The risk is that employees may feel undervalued if external titles don't match. Communicate the rationale clearly and offer a path to convert back if needed.

How often should we revisit the model?

Annually, at minimum. But also trigger a review when there is a major change in team size, business strategy, or turnover patterns. A model that worked for 50 people may break at 200, and vice versa.

Next actions: Audit your current career workflow—write down the explicit and implicit rules. Survey a sample of employees about their understanding and satisfaction. Identify one pain point (e.g., lateral move is unclear) and design a small intervention (e.g., a simple rotation policy). Test it for three months, measure the effect, and iterate. The goal is not perfection but continuous improvement.