+2  A: 

Sure, just define a route like so:

routes.MapRoute("{action}/{id}", new {controller="Home", action="Index", id=""});

The only problem is what about requests for your other controllers? For example, is

/Product/Foo

A request for HomeController.Product("Foo") or ProductController.Foo()?

You might need to use constraints to make the distinction clear.

Haacked