|
|
| |
Design Wiki™ & Core
Our fast track methodology covers all the bases
so your information design is robust and governable
|
|
The Design Wiki methodology creates a sustainable design base for your SharePoint implementation, as well as living documentation that directly supports recordkeeping compliance and audits. What you get:
|
|
Starting template |
A clone of our master designwiki, with over one hundred pages of design questions, options and answers, and links to other design documentation. |
|
|
Facilitation &
collaboration |
We facililiate honing your copy of the Design Wiki to meet your specific needs. You can use the collaboration assets, such as task lists, issues register and timelines, to enable you to manage progress. |
|
|
Compliance & governance documentation |
Design Wiki becomes your place to store recordkeeping decisions and documentation such as metadata standard mapping, that is required for Public Records Act compliance. |
|
|
Core - template build |
Content types, site, list & library designs agreed in the Design Wiki process are then built into templates for your site. |
|
|
Core - functionality |
Ability to copy or move content respecting metadata defaults, unique ID, search usability and more. For PRA, removing user deletion, record keeping mandatory metadata & locking down emails. |
|
|
|
| The iWorkplace Difference |
Knowledge transfer so you become more self sufficient
100+ design questions & default answers for doc mgmt, intranet, collaboration and know-how
Proven methodology, reference sites and satisfied customers
PRA compliance base built in, if you need it
|
| PRA audit feedback |
“You probably noted how interested (and impressed) the PRA auditers were, especially with the design process as documented in the Design Wiki"
Trish Brimblecombe
Whitireia Polytechnic |
|
|
| |
“DesignWiki really prompted us to start making governance and infrastructure decisions about the metadata for the project.
Having a template to work from meant we were aware of best practice but could still personalise and own the process, ensuring it suited the way we worked.”
Inge Jensen
Bay of Plenty Polytechnic |
|
|
