Executive Summary This work approaches the problem of selectively forgetting knowledge from a large language model (LLM) for the purposes of safety, copyright, security, or otherwise. Also known as machine unlearning, this entails training a model to forget certain elements of the dataset on which it was trained. Unlearning methods must be evaluated both in terms of the extent to which the information has successfully been forgotten, and the performance of the unlearned model on the remaining (retained) data. We build on the work of TOFU (Task of Fictitious Unlearning) [21], which provides a dataset and benchmark for evaluating unlearning techniques. We create a new, TOFU-inspired question–answer dataset for the task of machine unlearning. The new dataset includes 10,500 question–answer pairs relating to over 1,000 distinct, synthetic entities of several types. Each question–answer pair is tagged with the entities it refers to, with the graph representation of our dataset containing over 2,600 edges between different entities. We perform two experiments with our dataset. The first experiment aims to capture whether the difficulty of forgetting a concept from a LLM depends on its granularity. For example, is unlearning more likely to be successful if forgetting a single book, rather than the book's author (as an author is connected to multiple books)? We find that granularity does not have a tangible effect on model performance in our dataset. There may be a small effect from granularity on the difficulty of forgetting, but this is not statistically significant across our results. Our second experiment explores the knock-on effect of forgetting a relationship between two entities. For example, if unlearning has been run on a model to forget only who wrote a book, but not the book or author themselves, is the model worse at responding to other questions about that book or author? We find that the model performance is lower on questions that contain the entities pertained in the relationship, than on those that do not. 1
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.