# IT project management in the mid-market: roles, steering and an honest status > Why IT projects fail in mid-sized companies and what helps: fill the roles, limit the scope, document decisions, name risks early and tie completion to actual use. URL: https://techport.ai/en/it-beratung/einfuehren-und-veraendern/it-projektmanagement --- 1. [IT Consulting](/en/it-beratung)/ 2. [Rollout and Change](/en/it-beratung/einfuehren-und-veraendern)/ 3. IT projects that deliver [Rollout and Change](/en/it-beratung/einfuehren-und-veraendern) # IT projects that deliver By Redaktion techport.ai, IT-Beratung · Last updated on 21 August 2026 IT projects in mid-sized companies rarely fail for lack of methodology. They fail because the project lead does the job on the side, because the department gets no time, because decisions are deferred, and because the status stays green until it is red. Good project management at this scale is unspectacular: a few roles that are genuinely filled, a limited scope, a date on which decisions get made, and the willingness to speak about problems while they are still small. ## How you notice it * The project lead has taken the project on in addition to daily business. * The status has been amber for weeks without anything changing. * Decisions get deferred because the person with the authority is not present. * The scope has grown since the start, the deadline has not. ## Why this happens In the mid-market there are rarely people whose only job is project work. Projects are led by people who also run a department, and in case of doubt daily business wins because it is louder. On top of that comes a cultural component: in many companies a red status is read as personal failure rather than as information. The result is that problems get reported when they can no longer be solved. ## How we go about it 1. **Fill roles rather than name them.** Before the start we clarify who the sponsor is, who leads the project and with how much time, who decides on business questions in the department, and who will own the result afterwards. If one of those roles stays empty, we do not start. 2. **Limit the scope and sharpen the goal.** We cut the initiative so that a first usable result stands within a few months. Everything not strictly needed for that first result is visibly moved to a second stage rather than deleted. 3. **Steer honestly.** We work with short fixed meetings, a one page status report, a list of open decisions with deadlines and a risk list that is actually maintained. More important than the format is that reporting a problem carries no consequence for the person reporting it. 4. **Tie completion to use.** We declare a project finished when the old way is switched off, usage has been measured and operations have an owner. Before that it is not a completion but a handover to nobody. ## What you gain * Fewer projects that are formally finished and factually unused. * Early warning signals, because problems are allowed to be reported. * Results in stages, so value appears before everything is finished. ## From our projects The most reliable predictor for a project is not the plan but the time the department actually gets. If the key person in the department is scheduled alongside daily business and their cover has not been arranged, the deadline moves regardless of the method. We therefore agree in writing before the start which people are available with how much time and what will be left undone in daily business during that period. That agreement is uncomfortable and the single most effective factor for meeting deadlines. ## Häufige Fragen Do we need project management software? For one to three parallel initiatives a shared repository, a task list and a status report are enough. A tool pays off when several projects compete for the same people and you want to see capacity across them. A tool does not replace steering, it only makes the absence of steering more visible. What do we do with a project that clearly is not working? Decide early and openly whether to correct course or stop. Stopping a project is expensive, running it to a bitter end is more expensive. It helps to name the option of stopping at the outset and to define criteria for it. Then it is not a loss of face later but a planned option. ## Let us talk about IT projects that deliver In a thirty minute first call we work out where your biggest lever sits and whether we are the right people for it. [Arrange an initial call](/en/kontakt)[Our consulting](/en/so-funktionierts) ## Further reading [IT Strategy and SteeringPrioritising IT projectsHow a wish list becomes a portfolio: assess initiatives by benefit, effort and risk, plan capacity realistically, recognise dependencies and justify decisions.](/en/it-beratung/it-strategie-und-steuerung/projektportfolio)[Build and BuyGathering requirements properlyHow wish lists become solid requirements: processes as the starting point, prioritisation into must and should, acceptance criteria and a way to handle changes during the project.](/en/it-beratung/entwickeln-und-beschaffen/anforderungsmanagement)[Rollout and ChangeSupporting the changeWhy technically finished systems stay unused and what helps: involve those affected early, inform managers first, take resistance seriously and measure adoption after go-live.](/en/it-beratung/einfuehren-und-veraendern/change-management)[KnowledgeIT metricsDefinitions and formulas read the same way across the company.](/en/it-beratung/kennzahlen)[KnowledgeIT maturity checkKnow where your IT stands in ten minutes.](/en/it-beratung/reifegrad-check) Back to the field [Rollout and Change](/en/it-beratung/einfuehren-und-veraendern) Rt Written by [Redaktion techport.ai](/ueber-uns), IT-Beratung Mehr als 15 Jahre Erfahrung in IT-Projekten des Mittelstands, Auswahl und Einführung von Unternehmenssoftware, Aufbau von IT-Betrieb und Informationssicherheit in wachsenden Organisationen. [More about us](/en/ueber-uns) More from techport.ai [ Software Custom process software for mid-sized companies. ](/en/loesungen)[ HR consulting People processes and the systems behind them. ](/en/hr-beratung)[ IT maturity check Ten minutes to a clear position. ](/en/it-beratung/reifegrad-check)[ HR maturity check 24 statements, a result per field. ](/en/hr-beratung/reifegrad-check)[ Funding BAFA grant plus more than 50 programmes for delivery. ](/en/foerderung)[ Process in practice How workflows become reliable software. ](/en/sop-praxis)[ Data and AI Analysis, forecasts and assistance systems. ](/en/daten-ki)[ About us The people behind techport.ai. ](/en/ueber-uns)