Use cases are often perceived as an integral part of an objectoriented approach to software development, yet despite claims that objects fall naturally from the use case description [1], detailed guidance on moving towards design is rather limited. This paper outlines an approach which helps to tease out information necessary for design, that helps discover design classes which are often hidden, implicit or assumed.