<p>And if you do, can you give some background information on the implementation and the reasons for implementing this pattern?</p>

<p>The pattern is described in more detail in these articles:</p>

<ul>
<li><a href="http://msdn.microsoft.com/en-us/library/ms997506.aspx" rel="nofollow noreferrer">Microsoft Inductive User Interface
Guidelines</a></li>
<li><a href="http://msdn.microsoft.com/en-us/library/ms951103.aspx" rel="nofollow noreferrer">IUIs and Web-Style
Navigation in Windows Forms, Part 1</a> &amp; <a href="http://msdn.microsoft.com/en-us/library/ms951278.aspx" rel="nofollow noreferrer">Part 2</a></li>
</ul>

Yes - we had a problem in that many of the administrators of our software found it too difficult to use. To solve this we used Microsoft's WinForms IUI framework build a new configuration and management tool for our software.
User feedback has been extremely positive, particularly with everything being task driven - i.e. the links on our home page include thing like "Create new user", "Create new department" - rather then the user having to discover how to do this by clicking through a series of menus. Since the inductive interface is more similar to a web-browser (hypertext links, back/forward buttons) it seems much easier for new users to learn.