Quick Tip. I just installed Office on my home computer, and thought I’d share a helpful hint. I recommend the following options when installing Microsoft Office on your computer:
WARNING: Failure to disable Sharepoint may lead to missed expectations and general feelings of disappointment & disillusionment.
We’ve been hearing a lot of questions about how PBwiki can be used in the workplace. Rather than offer a boring list of suggestions, we’ve created this cool video to show how WE use PBwiki at our office.
Here are some tips:
1) Don’t email documents to your coworkers and then try to manage and integrate their responses. Instead put your document on the wiki and invite your colleagues to make changes and offer suggestions.
2) Brainstorm your ideas on a wiki — it’s easy to create a cohesive plan once all your ideas have been laid out and reviewed by the team.
3) Eliminate unnecessary follow up meetings by placing your plans on the wiki.
How do YOU use your PBwiki?! We will feature the best response in a PBwiki case study – so be creative!
We were combing through some data a few weeks ago and discovered something interesting: Over 1/3 of the Fortune 500 has used PBwiki. This is great news for our Small Business Edition — with so many Fortune 500 users, we’ve already seen small business users feeling more comfortable about security and safety.
So we’re turning to our PBwiki community: How should we spread the word about PBwiki in the Fortune 500 to small businesses?
Leave a comment on this post with a suggestion or example of how you would spread the word to business users. The best suggestion will win one free year of the PBwiki Small Business Edition!
Now that you’ve created your PBwiki, here’s a 60-second overview on how to create pages and upload files.
Uploading a file
To upload a file to your wiki, click “Edit page” and then “Attach file.” Free wikis have 10MB of storage space, while Premium wikis have up to 10GB of space.
Creating a new page
To create a new page, click “Edit page” and type in some words. Then highlight the words you’d like to link to (like “Schedule of Events”), click “Insert link,” and create a link to the new page.
See this process about 10% of the way through the video below:
You can also create a new page by clicking “New page,” but be sure to link to it so it’s not an orphan page! (If you accidentally create an orphan page, find all pages by clicking “All pages” at the bottom of your wiki.)
Bonus tip: Power users may want to click “Classic mode” to get a wiki-style editor. This will let you embed embed HTML and control formatting more closely.
[Note: PBwiki’s top priority is improving access controls. We’ll be releasing a new system in early November. Stay tuned for more details.]
PBwiki offers a number of ways to share your wiki with others.
To share your wiki using a single wiki password
Why you might do this
How to do it
Email the wiki URL to your friends and include the password. For example, “Hi all, to get to the planning wiki, visit http://yummy.pbworks.com — the password is fantasia”
Free or Premium users
Your wiki-wide password is the password you created when you signed up. Note that if you have a free wiki and you share the password, visitors will effectively be administrators of the wiki, with the ability to add pages, delete pages, and more. (They will not be able to delete the wiki. Only the wiki creator can do that.)
Premium users only
For more sophisticated access controls, upgrade to a Premium account. Premium users, click “Settings” >> “Passwords and access” to set passwords for readers, contributors, moderators, and administrators (Compare access levels here). For example, to give access to your co-workers to edit your wiki (but not delete pages), share the contributor password with them.
To share wiki access without requiring a password
Why you might do this
How to do it
Copy the magic link in your wiki and paste it.
Anyone who clicks the link will be given instant access without requiring a password. Note that…
To add specific users (with the ability to uninvite them)
Why you might want to do this
* You only want to invite specific people
* You want to keep track of who has access and who edited what
* You need the ability to immediately remove users
How to do it
1. Ask your users to create a PBwiki Identity at http://my.pbworks.com. (This involves setting up a username/password of their own.)
1.a. (For Premium wikis) Log in to your wiki, click “Settings” >> “Passwords and access” and set the level of password you want: Reader, Contributor, Moderator, Administrator (Compare access levels here).
2. Click users and invite them by email.
To add specific / mass amounts of users (without the ability uninvite them)
Why you might want to do this
How to do it
Click “Share this wiki” at the bottom of your wiki. You’ll be able to email large amounts of users, including directly from your web-based address book (e.g., Gmail, Yahoo). Free wikis will send full access to invitees, while Premium users can select more granular levels of access controls.
When it comes to building a collaborative wiki, there are certain elements that significantly increase your chances for getting others to contribute to your wiki. Here are the PBwiki best practices for getting participants to be fully engaged in your wiki.
Avoid Blank-Page Syndrome: Pre-fill your wiki with content.
Most people get scared by blank pages. We call this “blank-page syndrome,” which causes users to flee and never return. There’s a way around this: Just add some content to your wiki before inviting users. Consider adding an “About Me” page, a “What’s this wiki about?” page, and a few more welcoming pages. Not only will this help new users get situated, it will help you get experience editing your new wiki. We find the learning curve of successful wiki editors to be about 12-15 minutes.
Make the front page a landing page for navigation.
Your front page should have a short explanation of the purpose of the wiki and links to appropriate pages, not one long scrolling page. This helps in two ways: First, users tend to get overwhelmed when they first come to a wiki, so this approach lightens up the content on the page and directs them to the next step. Second, if you get large amounts of users on one page, they won’t be able to edit it at once. With multiple pages, the chances of two people trying to edit a page at the same time is lower. So keep a short front page with links to other pages.
Give users something concrete to do.
One user, “Michelle,” had trouble getting co-workers to participate in her wiki for over a year. Then she changed her approach: She asked users to change one line of the Frontpage. Participation skyrocketed and continues to be strong a year later. Consider creating a soft request, like asking users to add their name or to fix a single spelling error on the wiki page. They’ll be much more likely to try editing if they have a small nugget to accomplish first.
Making logging in as easy as possible.
The problem is not access controls — it’s creating something compelling enough to get people to contribute to your community in the first place. Make your wiki easy to access and worry about access controls after getting a few regular participants. (If you absolutely need ironclad business security, we do offer the PBwiki Small Business Edition.)
Get everyone to participate.
When you start a new wiki, you’ll find that some people will cling to old methods of communication. For example, some of our users report that their co-workers continued emailing them or asking others to “please put this on the wiki.” When people email you, point them to the wiki. The beauty of PBwiki is that the most current information is always on the wiki, so direct them to your PBwiki URL and encourage them to add it themselves. After 2-3 reminders — and seeing their co-workers actively using it — they’ll be much more likely to contribute to your wiki.
Remind your users that it’s ok to play.
Your wiki users will be nervous the first time they come to PBwiki, wondering if they’re going to mess something up or cause an irreversible change. Assure them that it’s ok to edit pages — PBwiki automatically tracks changes and allows you to reverse changes, so they should feel free to edit an existing page or create a new page. In fact, one of your goals might be for each user to create their own page!
Make PBwiki part of your day.
One of our most successful wiki editors added “It’s on the wiki! http://wikiname.pbworks.com” to his email signature, instant-message window, and on his website. When users messaged him, it was the first thing they saw. Consider putting your daily schedule or important notices on your wiki. When others see it used regularly, they’ll buy in, too.
Plugins allow you to add interactive widgets to your wiki like collaborative calendars, chat rooms, YouTube videos, photo shows, and more (full list here).
Bonus how-to videos: Insert voice chat, event planning, and general plugins (skip to 1:15).
Whether its a small team meeting or a huge 1,000 person conference, it’s important to have a specific roadmap to guide your discussion. Having an agenda lets participants know where they’re headed, and keeps everyone on track.
PBwiki is an awesome way to engage all of your attendees and shape the message that both you AND your participants want to discuss.
Here’s how:
1) Create a provisional agenda on a wiki page – posting the the call-in number and meeting time
2) Invite your participants to post their meeting materials and edit agenda items
3) Keep an eye on the edits and make changes when necessary
The Leadership Learning Community is a great example of how a national meeting was developed using PBwiki. Check out there results here.
As you can see the wiki agenda quickly becomes a dynamic, self organizing space where attendees can introduce discussion topics, decide how much time each topic receives and easily edit information as the meeting approaches.
During the meeting the online agenda can serve as a note-taking template, and when the meeting is completed, the notes are instantly available online. Everyone can review the agenda / meeting notes and provide feedback.
Why this saves time:
1) Don’t waste time emailing meeting minutes to people, or answering repetitive questions about discussion points, or dial-in numbers.
2) No need to collect meeting material – they’re on the wiki!
3) Wikis increase buy-in and participation in the meeting by involving the entire team in the planning stages.
