Software consulting · Anonymized example
Consulting for a product that needed a path, not another rewrite slogan.
The team knew the product had aged. A full rewrite was the loud option and a risky one. The engagement was software consulting: read the system, name what had to change, and sequence the work so shipping did not stop.
Situation
New features were slow because old decisions were undocumented. Proposals for a rewrite did not say what customers would get first.
Approach
I reviewed the product with the people who change it, separated risks that block delivery from cleanup that can wait, and wrote a sequence the team could fund.
What shipped
A written point of view: what to keep, what to replace, the first release that earns the right to continue, and the risks of doing it in the other order.
Outcome
The team had a plan they could argue with and then follow. The next build started from a shared sequence instead of a slogan.