Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/41/d94896425/htdocs/blog/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/41/d94896425/htdocs/blog/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/41/d94896425/htdocs/blog/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/41/d94896425/htdocs/blog/wp-includes/http.php on line 61

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 106

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/functions.php on line 31

Strict Standards: Non-static method K2::include_all() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/app/classes/k2.php on line 20

Strict Standards: Non-static method K2::include_all() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/app/classes/k2.php on line 21

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/header.php on line 6
Organizing Content & Expert Knowledge without Spending a Million Bucks at Boston KM Forum
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-includes/plugin.php on line 339


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 55


Organizing Content & Expert Knowledge without Spending a Million Bucks

Thursday, May 16, 2013, 4 - 6 p.m., Bentley University, Morison Hall, Morison Boardroom #300, 175 Forest Street, Waltham, MA 02451. Campus Map.

SPEAKER: Larry Chait, Discussion Leader

TOPIC: Small/medium businesses (SMBs) are heavily represented within our KM community of practice; we also have members who work within groups in larger enterprises with limited resources to pursue their knowledge initiatives. The theme of this meeting came recently from a single member, but over the years, similar inquiries have frequently appeared. The discussion will focus on practices for gathering, sharing, and leveraging knowledge through minimally invasive, lower-tech, less-expensive solutions. Larry has been harvesting examples and experiences for a couple of decades – and he is sure you have your own. Typical situations with cautions and remedies for handling them will round out the topic. Whether you support ten, a hundred, or a few thousand people, there are sure to be ideas that will prove of value to you from this discussion!

BIOGRAPHY: In addition to being the President of the Boston KM forum, Larry Chait is Managing Director of Chait and Associates, Inc., a consultancy that advises senior managers and their teams on achieving and sustaining high performance. He has over forty years of business-management experience. In his consulting work, Larry has helped executives and organizations manage change. His focus is on knowledge management, change management, and business process improvement. In addition, Larry supports clients as an executive and team coach. Prior to Chait and Associates, Larry was Vice President and Director of Arthur D. Little, Inc. He held positions including chief knowledge officer, director, and principal consultant. Before ADL, Larry was president of his own retail organization and vice president of product development for a national IT services company. Larry has authored three books, is a contributing author of “Managing the Learning Process of the Corporation” and “Knowledge Management in Practice: Connections and Context,” and is co-author with Lynda Moulton of an upcoming book on practical knowledge management. Larry received his A.B. in Economics from Cornell University and his M.B.A. from Harvard Business School.

PLEASE PLEASE Register even if you are not certain you can attend so we have an accurate estimate of attendees for handouts. If you then make a decision not to attend, please use the registration link and note in the comments field that you will not attend.

NOTE: The registration page has changed and you will be directed to another site where the registration form resides. It is now hosted by lwmtechnology.com and is legitimate.

Registration Form for Thursday

Registration Comments (Cost, time, meeting format)

0 Responses to “Organizing Content & Expert Knowledge without Spending a Million Bucks”


  1. No Comments

Leave a Reply