Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Measuring the waits a hiring process creates, and keeping the record it owes Four working days of internal approval are three weeks of silence on the other side, and almost every complaint about hiring is a complaint about that gap rather than about the decision at the end of it. Recruitment administration is a queue with people in it, and the work divides into the part that shortens a wait and the part that shortens the record. Only the first is worth doing. Every process failure a small employer actually suffers, the candidate who was never told, the shortlist nobody can reconstruct, the panel slot that took eleven days to find, is located at a nameable waiting point and can be measured in days by whoever owns it. A chat model helps with the language sitting around those points: an advertisement drafted from a requisition, four hundred applications turned into a scheduling problem, the reply that was never sent. It must be kept away from the judgement at the centre, because a ranking that looks reasonable is the most expensive artefact in this subject and the hardest to argue with six months later. Audiences: The person who owes four hundred replies — Posted one role, received four hundred applications, shortlisted six, and told none of the other three hundred and ninety-four anything. Knows it is wrong, has no hour in the week where writing that correspondence fits, and will do the same thing on the next requisition. The person waiting on a panel — Has a shortlist and cannot convene three people in one room inside a fortnight. Every day of that fortnight is a day a preferred candidate spends accepting somebody else's offer, and the delay is invisible internally because everyone involved is busy and nobody is idle. The person asked why, six months later — Is asked to explain a hiring decision made half a year ago and finds a requisition, an offer, and nothing in between: no screening notes, no dated shortlist, no record of what the panel was asked to weigh. The process was followed and none of it was written down. Note: written from Indonesian operator context. Frameworks apply broadly to other emerging-market and SME settings.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.
Adaptive AI agents can help make BIM data more machine-readable by navigating IFC models, interpreting inconsistent information, and mapping it to defined standards. In this blog, Alok Rawat shares findings from a real-world pilot in construction workflows. The post Adaptive AI Agents in Construction Workflows appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.