Emily is feeling rebellious. Emily - the embodiment of many young business people the authors have worked with on system projects - faces a wall of "you don't understand how complex it is". She is told: "You do not have enough experience to make changes", "Best we keep going with the current work the way it is", and "We will think about improvements later." Emily becomes disillusioned and disempowered. Emily's Rebellion presents a new method of removing the complexity from business processes and information systems called the 'Transaction Pattern'. Emily has learned about Service Design and loves it, but she needs a way to bridge the gap between her customer-focused service blueprint and the technical-minded developers. The Transaction Pattern is Emily's bridge. It breaks down a service design into transactions and then into a generic pattern of phases and tasks that commonly recur. This structured approach, based on the pattern, readily specifies business requirements for system development and process implementation. Emily's Rebellion seeks to embolden people like Emily who are required to inhabit the space between the everyday operations of their business and technology 'improvement' and digitization projects. You can effect change today with simple steps - it does not have to be so complex. Walk with Emily as she discovers a new path to get better business outcomes from IT projects.