A new title represents genuine authority only when the company attaches decisions, access and accountability to it. If the work expands while pay and control stay where they were, the title is cheaper compensation.
Consider Sena, an invented composite drawn from a pattern I have seen in small product teams. At 4:40 on a Thursday afternoon in Accra, she sat in a payroll meeting with her sketchbook closed beside her laptop. She had joined as a UI/UX designer, but the founder was offering her a Product Operations Lead title instead of the raise she had requested.
The founder described the title as recognition. Sena heard additional work: coordinating releases, chasing customer feedback, maintaining the roadmap and translating between engineering and sales. Payroll would stay unchanged until the next funding milestone.
That milestone had no date.
Sena had until the following morning to accept. Refusing could mark her as someone unwilling to grow with the company. Accepting could leave her responsible for delivery failures she lacked the authority to prevent.
The title needed a decision attached to it
I have watched roles change quietly inside early-stage companies. A designer starts attending sales calls because customers explain workflow problems there. Then she joins sprint planning because engineering needs context. Soon, the founder depends on her to decide what reaches the next release.
The job has already changed before anyone discusses the title.
That does not automatically make the new title empty. Product operations can be a meaningful move for a designer who wants broader responsibility. It can create useful exposure to commercial decisions, delivery constraints and customer evidence. It can also place someone in the middle of every disagreement while leaving each functional lead free to ignore her.
Sena asked one question: “Which decision becomes mine on Monday?”
The room went quiet.
Could she remove an item from the release when engineering capacity changed? Could she require sales to record customer promises? Would she attend the meeting where hiring and runway shaped the roadmap? Who would explain her authority to the rest of the team?
The founder could not answer all four. He had imagined the activities in the role, not the decisions.
That gap mattered more than the wording on the employment letter.
Responsibility without access creates a blame position
Small teams often distribute work faster than they distribute information. One person becomes responsible for keeping a release on track, yet still hears about a promised customer feature after the contract is signed.
A Product Operations Lead cannot coordinate around decisions she never sees. She needs access to the discussions that create the constraints: customer commitments, engineering capacity, hiring plans and changes to the product sequence.
This resembles the problem in What Product Memory Disappears When a Designer Leaves?. Design work often contains far more product knowledge than the job title suggests. Companies notice that knowledge when they need someone to hold several parts of the product together. Recognition arrives late, sometimes after the employee has already carried the work for months.
Sena opened her sketchbook and divided a page into three columns: decisions, access and measures.
Under decisions, she wrote release scope and feedback priorities.
Under access, she wrote commercial commitments, engineering planning and founder review.
Under measures, she rejected “keep teams aligned.” That phrase could absorb every delay in the company. She proposed concrete measures tied to work she could influence: unresolved release dependencies, recorded customer feedback and product commitments made without delivery review.
The conversation changed. They were no longer negotiating the emotional value of a title. They were defining a job.
Deferred pay needs a trigger, not a promise
The hardest part remained the raise.
Early-stage companies sometimes lack the cash to match a larger role immediately. I understand that constraint. Runway can force an honest choice between retaining a capable person and preserving enough cash to reach the next customer or funding decision.
Ambiguity makes that trade unfair.
“After funding” leaves the employee carrying the downside while the company keeps every option. Funding may arrive late, arrive under different terms or never arrive. By then, the expanded role has become normal.
A useful deferral needs a trigger the employee can verify. It could be a specific company event, a scheduled compensation review or a temporary scope that ends on an agreed date. The agreement should also state what happens if the trigger never occurs.
Sena proposed a written trial period for the role. During it, she would receive the stated decision rights, attend the relevant meetings and stop carrying two design projects that no longer fit. The compensation review would happen on a fixed date, independent of whether funding had closed.
The founder hesitated. Removing design work meant admitting the company could not receive product operations leadership and the same design output for one salary.
For a few minutes, the offer looked likely to collapse.
Then he crossed one project off her workload.
Monday revealed whether the agreement was real
A title becomes credible through other people’s behaviour. The employment letter helps, but the first test happens when sales makes a product promise, engineering objects and someone asks who decides what moves.
On Monday morning, the founder introduced Sena’s remit to the team. When a proposed customer request threatened the planned release, he asked her to assess the tradeoff before anyone committed to it.
She had access to the conversation and permission to change the outcome.
Her pay had not increased yet. That unresolved part remained written down, with a date rather than optimism holding it in place. She also knew what she would do if the company missed the agreement.
If you receive a larger title in place of a raise, take out a blank page before you accept. Write three headings: decisions, access and compensation trigger. Leave any column empty, and the offer is telling you exactly where the risk sits.
Comments
No comments yet.