Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

SYSE.24:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWorking symptomRepair
Make-or-buy word comparisonRows say buy, build, outsource, AI, or reuse without the result-bearing arrangement behind them.Work backwards from acceptance, vary the consequential supply boundary, and follow the resulting whole forwards before summarizing it in the common account.
Compatible parts, impossible wholeEach supplier or Work item looks qualified, but data meaning, configuration, timing, or shared resources do not fit.Identify the failed join and compare actual repairs with their whole resource and support consequences.
Unanswered condition becomes trueA partial quote or late answer is treated as confirmation of operator availability, support, or usable rights.Retain only the supported part, expose the decisive gap, and choose an available alternative, bounded probe, restricted commitment, or reroute.
Demonstration versus production comparisonA polished external demonstration is compared with unfinished but fully burdened internal work.Apply the same operating conditions, configuration, acceptance evidence, integration, support, and exit basis.
Award as resultSupplier selection or contract award is reported as if the System, Work, access, capability, or episteme had been obtained and accepted.Keep commercial selection, Work, production, integration, acceptance, and use as separate results.
Provider absorbs engineeringOutsourcing is treated as removal of interface, configuration, assurance, affected-System, and change responsibility.State what remains with the receiving project and which provider result supports each reliance.
AI as an arrangementAn AI Agent is a peer row beside purchase and internal development.Place the Agent inside each arrangement where it may perform named Work; state capability, access, authority, evidence, stop, and recovery.
Method development as free supportA required new Method is hidden inside an option with no time, evidence, or capability consequence.Treat it as a separate enabling realization branch, or as the sought result when Method development is the decision itself.
Lowest visible pricePurchase or provider price wins while integration, support, knowledge, opportunity cost, exit, and displaced capability remain uncounted.Restore parity and obtain the financial and specialist results that can change the choice.
One scalar hides a protected conditionA weighted score compensates for a safety, authority, evidence, or exit failure that the receiving use cannot accept.Keep thresholds and partial order visible; reject arrangements that violate protected conditions.
Procurement umbrellaSystems Engineering silently chooses tender, contract, incentive, legal duty, financing, organization, or operating policy.Use an applicable specialist result for its consequence for the obtaining decision. Request a missing result when obtaining it is warranted.
Endless option inventoryThe team keeps expanding market and technology lists after no new arrangement can change the next choice.Use C.19 for exploration policy and C.11 for the bounded probe-or-choose stop.