[Sigia-l] What do you call that place between the database and the live site?

[Lisa Goldberg]

Jay,

I have a few thoughts regarding the "sandbox" thread. I am an IA who has a
fair amount of experience working with custom content management systems. I
also worked briefly in a RUP environment, so I think I understand where
you're coming from. However, IMO the "sandbox" environment does not add much
to the UCD process until you are near the end of the design cycle and can
usability-test your designs for validation.

Furthermore, if usability testing uncovers serious problems, changes might
be required to the requirements as well as the design. Is it worthwhile to
set up that sandbox until you have validated the design and requirements in
the first place?

Someone mentioned the problem of content not fitting the templates. A
sandbox tool would be helpful in that situation. But even better would be a
fully developed UCD process so that you don't run into those snags with a
content-driven site. Templates should not be developed until content
requirements are in place. If your team is not generating the content, then
someone also needs to work with the client to ensure that their content
meets the agreed-upon requirements. This effort may require the combined
efforts of an RA, IA and content specialist, depending on how things stack
in your organization. In my experience this process cannot be automated and
it's crucial to the successful launch of a content-driven site. It's also
critical for the RA, IA and developers to collaborate before development
begins.

I can think of a few places where automation would be helpful, however:

(a) If you are redesigning a site that is already dynamic, it would be nice
if that site could generate a content index for inventory purposes. I have
not worked with a CMS that exported file information in hierarchical format.
Has anyone else?

(b) If you have the time and budget to run a usability test on the
prototype, it helps to test that prototype onscreen, as long as your costs
for doing so are not more expensive than designing and testing on paper. You
need to factor in the costs for changes after the usability test.

To sum up, I think that the sandbox is best used for small QA adjustments
near the end of the design process, unless your IAs prefer to design using
this tool and it is cost-effective for them to do so.

Other insights welcome.

Sincerely,
Lisa

-----------------
http://www.lisagoldberg.info