The purpose of the LKNConnect Role Profile is to clearly define what an individual or organizational role is responsible for, what authority accompanies that responsibility, how the role interacts with others, how the individual can be contacted, and what successful performance looks like.
A Role Profile is not necessarily a traditional employee job description.
LKNConnect operates through a network that includes:
The Role Profile provides one consistent framework that can be applied across these different relationships.
Every important LKNConnect role should answer five fundamental questions:
What am I responsible for?
What decisions can I make?
Who do I work with?
How do people reach me?
How do we know the role is succeeding?
The purpose is clarity — not bureaucracy.
If Responsibility Is Unclear, Accountability Is Impossible.
A Role Profile should be created whenever an individual or organization assumes an ongoing responsibility that materially affects LKNConnect.
This may include:
Not every occasional volunteer, guest, interview subject, or one-time service provider requires a Role Profile.
The test is simple:
Does this person or organization own an ongoing LKNConnect responsibility?
If the answer is yes, the role should eventually be documented.
Every Role Profile should identify the type of relationship involved.
Possible categories include:
Individual holding an ownership interest in LKNConnect.
Individual with formal executive operating authority.
Individual providing ongoing strategic counsel without executive operating authority.
Individual responsible for recurring organizational processes or activities.
Individual responsible for recurring LKNConnect content or programming.
Individual helping LKNConnect identify stories, developments, needs, people, businesses, and opportunities throughout the community.
Individual helping identify businesses, organizations, or individuals that may benefit from LKNConnect visibility services and helping open appropriate relationships.
Individual directly involved in developing, supporting, or closing revenue opportunities.
Individual responsible for maintaining the primary relationship with a client.
Individual providing recurring support to a specific LKNConnect program.
Individual or organization providing ongoing professional video-production capability.
Individual or organization responsible for ongoing technology, programming, CRM, automation, website, or systems development.
Individual or organization whose relationship contributes ongoing expertise, relationships, technology, business opportunities, or organizational capability beyond a traditional vendor relationship.
A person may appropriately belong to more than one category.
Every LKNConnect Role Profile should contain the following sections:
Using the same structure for each role allows LKNConnect to compare responsibilities, identify gaps, and reduce organizational confusion.
Every profile begins with basic organizational information.
Role Title
Name
Organization / Company
Role Category
Program / Functional Area
Accountable To
Works Closely With
Effective Date
Last Reviewed
This establishes where the role fits within the LKNConnect Operating Network.
Every Role Profile should contain current contact information appropriate to the individual’s relationship with LKNConnect.
Recommended fields include:
Primary Email
Primary Phone
Organization / Company
Website
Preferred Contact Method
Best Time / Availability
Emergency / Time-Sensitive Contact Method
Contact information should also be classified as:
Internal Use Only
Approved for Public / Business Use
or
Both
Personal contact information provided for internal TEAM use should not automatically be published or distributed externally.
Keep the Information Current.
Know How to Reach the Person.
Protect Information That Is Not Intended for Public Use.
In two or three sentences, explain why the role exists.
The Role Purpose should answer:
What value does this role provide to LKNConnect?
Avoid simply listing tasks.
The purpose should describe the contribution the role makes to the organization.
Identify the major responsibilities owned by the role.
Whenever possible, responsibilities should begin with clear action language such as:
The objective is to describe ownership, not simply activity.
Identify what decisions the role may make independently.
Examples might include:
Also identify decisions requiring Executive Leadership approval.
Examples may include:
Responsibility Without Appropriate Authority Creates Frustration.
Authority Without Accountability Creates Risk.
Identify responsibilities according to their normal frequency.
Activities requiring regular daily attention.
Activities normally completed each week.
Activities reviewed or completed each month.
Activities requiring periodic strategic or performance review.
Responsibilities triggered by a particular event, client, opportunity, issue, or organizational need.
Not every role requires responsibilities in every category.
A Role Profile should describe what successful performance looks like.
The focus should be on results, not simply activity.
For example:
Instead of:
Posts content every week.
Use:
Delivers assigned content consistently, on schedule, and at a quality appropriate for LKNConnect publication.
Instead of:
Enters leads into CRM.
Use:
Ensures qualified opportunities are accurately captured in the CRM so appropriate follow-up occurs.
LKNConnect uses a hybrid approach to performance measurement.
Different roles require different forms of accountability.
Use measurable expectations whenever practical.
Examples:
Possible measurements include:
Possible measurements include:
Possible measurements include:
These roles should normally be evaluated through:
Artificial quotas should not be created simply to make an advisory relationship appear measurable.
Measure What Matters.
Do Not Measure Simply Because Something Can Be Counted.
Identify the people or groups with whom the role must work effectively.
These may include:
This section helps prevent organizational silos.
Identify the systems necessary for the role.
Examples may include:
A role should have access only to the systems necessary to perform its responsibilities.
Each Role Profile should define how important information moves through the organization.
The role should know:
What information must I communicate?
Who needs to know it?
When do they need to know it?
Important organizational information should not remain solely inside personal text messages, emails, notebooks, or individual memory when others require access to it.
Where appropriate, important information should be captured in the CRM or another approved organizational system.
If the TEAM Needs to Know It, the TEAM Must Be Able to Find It.
Every critical role should identify what happens when the Primary Owner is unavailable.
The Role Profile should answer:
Who is the backup?
Where is the information stored?
Can another person continue the process?
What would stop if this individual were unavailable?
A process that exists only in one person’s memory is not yet an organizational system.
LKNConnect recognizes that individuals may legitimately serve in multiple capacities.
Current examples include:
David Beard
COO + Financial Management + Business Development + Sales + Contributor
Margi Kyle
Executive Advisor + Charter TEAM Member + Contributor
Lynn Marshall
Sales Consultant + Contributor + Community Ear + Visibility Strategist™
David Woodruff / Genesis Film
Contributor + Around the Lake + Video Production Partner
Greg Prinz & Marko Brutus / Chapter One Films
Contributors + Chapter One + Video Production Partners
An individual does not necessarily require a completely separate document for every responsibility.
Related responsibilities may be combined into one Role Profile when doing so remains clear.
Separate profiles should be created when responsibilities involve significantly different authority, accountability, or organizational relationships.
Unless otherwise defined, recurring LKNConnect Contributors are expected to serve three broader functions.
Provide useful, authentic, locally relevant content.
Serve as LKNConnect’s ears throughout the community.
Recognize people, businesses, stories, relationships, and opportunities that may benefit the community or LKNConnect.
This creates the standard Contributor model:
Content Creator + Community Ear + Visibility Strategist™
Not every Contributor is expected to become a traditional salesperson.
Contributors create value by opening doors, building relationships, and helping LKNConnect recognize opportunities.
When a TEAM member introduces and develops a new client relationship, that individual normally becomes the Primary Relationship Owner unless responsibility is formally reassigned.
Relationship ownership means:
Relationship ownership does not mean personal ownership of the client.
The Individual Owns the Relationship Responsibility.
LKNConnect Owns the Client Commitment.
A Role Profile should ultimately be reviewed with the person responsible for the role.
The objective is not simply to hand someone a document.
The objective is mutual understanding.
The discussion should confirm:
I understand why my role exists.
I understand what I own.
I understand what decisions I can make.
I understand what requires approval.
I understand who I work with.
I understand what successful performance looks like.
Where appropriate, the Role Profile may be acknowledged by both the Role Owner and LKNConnect leadership.
Role Profiles should be reviewed whenever:
At minimum, critical Role Profiles should be reviewed annually.
The review should ask:
Is this role still necessary?
Is the purpose still accurate?
Does the right person own it?
Has responsibility changed?
Can any portion be delegated or automated?
Are expectations clear?
Is the contact information current?
Role Title: __________________________________
Name: ______________________________________
Organization / Company: ______________________
Role Category: _______________________________
Program / Functional Area: ____________________
Accountable To: ______________________________
Works Closely With: ___________________________
Effective Date: _______________________________
Last Reviewed: _______________________________
Primary Email: ________________________________
Primary Phone: ________________________________
Organization / Company: _______________________
Website: _____________________________________
Preferred Contact Method: _____________________
Best Time / Availability: ______________________
Emergency / Time-Sensitive Contact Method: _____
☐ Internal Use Only
☐ Approved for Public / Business Use
☐ Both
Daily: ______________________________________
Weekly: _____________________________________
Monthly: ____________________________________
Quarterly: __________________________________
As Needed: __________________________________
Backup: _____________________________________
Critical Information Stored At: _______________
Continuity Requirements: ______________________
Role Owner: __________________________________
Leadership Review: ____________________________
Review Date: __________________________________
Next Review: __________________________________
As individual Role Profiles are completed, LKNConnect should maintain a centralized Master TEAM Contact Directory.
The directory should contain only the information necessary for internal organizational communication.
Recommended fields include:
The Master TEAM Contact Directory should be updated whenever a Role Profile is added or changed.
This prevents contact information from becoming scattered among individual emails, text messages, personal address books, and documents.
The Contact Directory should be treated as an internal operating resource unless specific information has been approved for public or business use.
Appendix B establishes the standard.
It does not require LKNConnect to immediately create individual profiles for every person in the Operating Network.
Implementation should occur in stages.
Create Role Profiles for:
Founder & CEO
COO
These roles carry the greatest organizational responsibility and decision authority.
Create profiles for:
Sales Consultant
Visibility Strategist™
Client Relationship Owner
These roles are increasingly important as LKNConnect develops its sales, CRM, Business Visibility Audit™, and lead-generation systems.
Create standard profiles for:
Contributor
Video Production Partner
Technology & Development Partner
Strategic Partner
These Master Profiles can apply to multiple individuals where responsibilities are substantially similar.
Create individual profiles when someone’s responsibilities differ materially from the applicable Master Profile.
This approach provides organizational clarity without requiring LKNConnect to create unnecessary paperwork for every individual relationship.
Document the Critical Roles First.
Standardize What Can Be Standardized.
Individualize Only Where It Adds Value.
Every important LKNConnect responsibility should ultimately have:
A Purpose.
An Owner.
Defined Authority.
Clear Expectations.
Current Contact Information.
Appropriate Measurement.
Required Relationships.
A Communication Process.
A Continuity Plan.
The objective is not to create bureaucracy.
The objective is to prevent confusion.
Define the Role.
Assign the Responsibility.
Provide the Authority.
Keep the Contact Current.
Measure What Matters.
Document the Knowledge.
Build the Backup.
Create Accountability Without Creating Bureaucracy.
LKNConnect Operating System™
Appendix B — Role Profile Template
Master Edition — Version 1.0
