You can read a lot online about different forms of content mockups. There are:

• Paper mockups
• Feehand/Illustrator Mockups
• A variety of diagram planners

And of course, the new cool thing: HTML mockups.

HTML mockups are great. In fact, they’re at the core of what makes Jumpchart a good idea. They have momentum into the build phase, and clients understand what you’re trying to tell them better. html Mocks have some issues though:

• You have to throw together a workable CSS template for your mock.
• If a client changes their mind about navigation, you have to manually update a lot of pages.
• When the client wants to move content, or delete sections, you again have to make manual changes.
• You still have to find spots for all of the deliverables.
• and the biggest one… html mocks are not collaborative…

Of course some of these things eventually work themselves out. Maybe you make some include files that help you handle the inevitable navigation changes. Some of the other issues as well can be handled with some creative work-arounds, and maybe some patience.

We would never say that Jumpchart is the only way to plan projects. There are virtually infinite ways to organize, and plan your projects. We would however say that Jumpchart is simply the easiest, most rapid, and effective way to get your ideas into a logical communicative web based format that has momentum into the build phase.