Indeed, the way I try to avoid it is to make public commitments (that are achievable but timely) which will become obvious to others. This will include mileston

Indeed, the way I try to avoid it is to make public commitments (that are achievable but timely) which will become obvious to others. This will include milestones along the way. Possibly the commitment won't be all to one person, maybe I'll be telling someone that reports to me that they can expect a list of requirements by X, then someone else that we will review the first wire frames by Y and then those I report to that they can expect to feedback on Z date. This keep me continually moving and fits nicely with the scrum/lean methodologies that we follow.