Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 199

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/rlsnetnt/public_html/blog/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673
{"id":900,"date":"2013-08-23T07:57:17","date_gmt":"2013-08-23T07:57:17","guid":{"rendered":"http:\/\/rai.net.in\/blog\/?p=900"},"modified":"2013-08-23T11:36:40","modified_gmt":"2013-08-23T11:36:40","slug":"moving-with-times-professionalizing-family-run-businesses","status":"publish","type":"post","link":"https:\/\/blog.rai.net.in\/moving-with-times-professionalizing-family-run-businesses\/","title":{"rendered":"Moving with times \u2013 Professionalizing Family Run Businesses"},"content":{"rendered":"

<\/code>\u201cProfessional businesses put the customer and the organization above self interest. They are characterized by objectivity of decision making\u201d<\/em><\/h2>\n

 <\/p>\n

 <\/p>\n

\"Moving<\/a><\/p>\n

 <\/p>\n

This was the perspective provided by Prof. S Sriram on the process of professionalizing Family Run Businesses (FMB\u2019s) @ CRS 2013.<\/p>\n

Some facts around Family Managed Businesses (FMB\u2019s):<\/em><\/h2>\n

 <\/p>\n

 <\/p>\n

    \n
  • Nearly all firms start as family businesses.\u00a0 No firm on earth started out as a corporate.<\/li>\n<\/ul>\n
      \n
    • 33% of S&P listed companies still have 1 family member onboard. Globally, 70 to 90% of GDP comes from family run businesses.<\/li>\n<\/ul>\n
        \n
      • FMB\u2019s are more stable during economic recessions.\u00a0 When compared against non FMB\u2019s on profitability parameters \u2013 they tend to outperform, especially during downturns in the economy.\u00a0 However, during the uptick in the economic cycle, they also grow slower than their non FMB counterparts. This is a function of the inherent conservative DNA and focus on capital preservation.<\/li>\n<\/ul>\n

         <\/p>\n

        \u201cFamily Managed Businesses are more stable and profitable during economic recessions, but they also grow less during economic upturns.\u201d \u2013 Prof S Sriram, Great Lakes.\u00a0<\/em><\/strong><\/p>\n

        Professionalization<\/b>:\u00a0 The word \u201cProfessionalization\u201d has different meanings. In many cases, FMB\u2019s believe that if they get an outside CEO they have \u201cprofessionalized\u201d. In other cases the word is applied to any structure which separates ownership from management.\u00a0 However, we believe that Professionalizing is a mindset and an attitude \u2013 it\u2019s about how you think and take decisions. It has nothing to do with ownership \/ management or structure (i.e. whether the company is a private or Public Sector Company). \u201cHow objective you are in decision making determines how professional you are.\u201d<\/p>\n

         <\/p>\n

        \u201cHow objective you are in decision making, determines how professional you are\u201d \u2013 Prof S Sriram, Great Lakes.\u00a0<\/em><\/strong><\/p>\n


        Why companies professionalize<\/b>:\u00a0 The usual motive is to deal with the pressures introduced by growth. Growth vs control is the classic dilemma that family businesses face especially, because in India, not only are 80% of businesses family owned, they are also privately held.\u00a0 Some businesses look at the listing process to introduce not only external capital but also governance. Making a company list-worthy usually involves bringing in an external \u2018professional\u2019 CEO \u2013 this is one of the popular definitions of \u2018professionalizing\u2019.<\/p>\n

         <\/p>\n

        Challenges<\/b>: Key challenges are around success planning, \u201cletting go\u201d and finding a convincing answer to the question \u201cWhy professionalize?\u201d.<\/p>\n

         <\/p>\n

        Succession planning<\/b>: 15% of FMBs globally survive to the 3rd\u00a0generation. The biggest challenge is therefore succession planning and management \u2013 i.e. changing from an entrepreneurial mindset to a managerial leadership mindset.\u00a0 This change is evidenced\u00a0when the decision making process moves from individualized to a data based, consensus making decision process.<\/p>\n

        \u201cWe believe that the definition of a professional entity is one which places the interest of the consumer and the organization above self-interest. The decision maker may or may not be the owner of the company. This is easier said than done\u201d.<\/p>\n

         <\/p>\n

        \u201cThe challenge of \u2018letting go\u2019 \u2013 at its simplest level is answering the question of \u201cWhat am I going to do with my time, now that I am no longer actively managing the business?\u201d\u201d \u2013 Prof S Sriram, Great Lakes\u00a0<\/em><\/strong><\/p>\n

         <\/p>\n

        \u201cLetting go<\/b>\u201d:<\/b>\u00a0Once the owners professionalize the second challenge is about \u2018letting go\u2019 \u2013 at its simplest level its answering the question of \u201cWhat am I going to do with my time, now that I am no longer actively managing the business?\u201d.\u00a0 Any attempt to professionalize will not work unless there is a concrete answer to the above.<\/p>\n

         <\/p>\n

        \u201cWhy professionalize<\/b>\u201d.<\/b>\u00a0 Often this is the biggest challenge to starting the process.\u00a0 While the usual answer is \u201cscale is the tipping point\u201d \u2013 most entrepreneurs chose control over growth. The internalized, often un-articulated reason is also because they believe that \u201cif something isn\u2019t broken, don\u2019t fix It\u201d. In other words, scale can be subverted to control.<\/p>\n

        \u201cThe unarticulated reason for not professionalizing is that many entrepreneurs believe that scale can be subverted to control\u201d \u2013 Prof S Sriram, Great Lakes\u00a0<\/strong><\/em><\/p>\n

         <\/p>\n

         <\/p>\n