I'm already doing test automation. Why should I use keyword-driven test automation?

Traditional test automation techniques provide a significant improvement over manual testing, but require tests to be created by test automation engineers with programming skills for all but the most simple of applications. Test designers traditionally document their test cases in a word processing application, and then pass these documents to automation engineers who code automation scripts.

Using the traditional test automation approach can introduce a number of problems into the testing effort:
With Action Based Testing:

In a TestArchitect's test module, test cases are organized in a worksheet format. Each worksheet is both an executable test and documentation of the test. This further reduces the maintenance required whenever the application is updated.