Diego ETB

Diego ETB

Meeting Overview and Objectives

Initial Meeting Context

  • The speaker reflects on the rarity of their meetings, noting this is the second time they have spoken in a formal setting.
  • They express hope for successful collaboration this time, acknowledging past challenges in securing talent.

Company Background

  • The company, ETB, has been operational for approximately 142 years with a small team of around 16 people.
  • They are currently developing an internal content strategy aimed at cultural transformation within the organization.

Cultural Transformation Strategy

Key Components of the Strategy

  • The strategy focuses on three main pillars: emotional repair, cultural elements, and close management.
  • Emotional repair includes aspects like growth mindset, relationships, mental health, and physical health.

Cultural Engagement Initiatives

  • Examples include speed dating sessions to improve communication among employees and enhance synergy within teams.
  • The approach emphasizes dynamic content consumption similar to external media preferences—engaging formats that educate and entertain.

Content Delivery Methods

Innovative Content Formats

  • Proposed formats include podcasts (30 minutes), short TikTok-style videos (up to 3 minutes), and snackable storytelling emails.
  • A user-friendly web platform is envisioned where employees can access diverse content tailored to their interests.

User Engagement Strategies

  • Employees will answer questions after consuming content to earn points redeemable through partnerships with various companies.
  • This system aims to encourage participation by making learning enjoyable while addressing employee concerns about studying.

Emotional Well-being Focus

Addressing Employee Concerns

  • There’s a strong emphasis on emotional repair due to recent workforce reductions impacting morale; many employees feel anxious about job security.

Employee Benefits and Internet Service Insights

ETV's Employee Benefits

  • ETV is highlighted as a unique employer, offering extensive benefits such as two schools for employees, 45 days of vacation bonuses (three full bonuses per year), and full salary bonuses instead of half.
  • Additional perks include prepaid health plans, a vacation center in Girardot, and financial support for further education like master's degrees or undergraduate studies.

Internet Service Comparisons

  • The speaker contrasts ETV's internet service with competitors, noting that while ETV provides good service, response times for repairs can be slow compared to others like Claro.
  • Personal experience indicates that having both services is beneficial; when one fails, the other can provide backup until repairs are made.

Content Consumption Strategies

  • There’s a discussion about targeting younger audiences through content marketing. The speaker believes traditional methods may not effectively engage this demographic due to its niche nature.
  • The goal is to create engaging content that encourages users to revisit videos or tutorials on their mobile devices from home.

Platform Functionality and User Roles

  • A proposal is made to separate discussions into resource management and technical aspects of the platform being developed for user engagement.
  • Users would create accounts using their ETV email addresses. A streamlined login process via confirmation links is suggested to enhance user experience.

Content Creation and Distribution Challenges

  • Questions arise regarding the types of content being prioritized. While video content is emphasized due to high consumption rates, there are also plans for articles based on audience needs.
  • Current distribution channels are limited; previously used Microsoft social networks have transitioned away from internal platforms. Email and corporate WhatsApp groups are now primary communication tools.

Video Hosting Considerations

  • Suggestions are made regarding where to host video content. YouTube is recommended for its ease of use and ability to keep videos private while still accessible through links.
  • Concerns about potential costs associated with alternative hosting platforms like Vimeo highlight the need for cost-effective solutions in distributing company content.

Content Strategy Discussion

Overview of Content Hosting

  • The discussion begins with the suggestion to use Vimeo, but it is clarified that YouTube is the preferred platform for hosting content due to server cost concerns.
  • It is noted that there are different types of users: administrators who create and upload content, and collaborators who only consume it.

Types of Content Prioritized

  • The team has prioritized various content formats including videos, emails, articles, and podcasts.
  • A podcast is planned to be hosted by the VP of Human Resources, who is described as an excellent communicator.

Podcast Development

  • There’s a consideration for using both YouTube and Spotify as potential platforms for the podcast.
  • The advantage of uploading to YouTube includes the ability to keep content private until it's ready for public release.

Content Structure and Strategy

  • The conversation shifts towards defining three main pillars of content, each containing at least five subtopics.
  • When creating videos or articles, a subtopic will be selected that aligns with one of these pillars.

User Navigation Considerations

  • A key decision involves how content will be displayed; options include infinite scrolling versus categorized listings.
  • Implementing filters based on subtopics may enhance user experience by making navigation more intuitive.

Audience Targeting Challenges

  • There's a recognition that while categorizing by audience (e.g., parents vs. non-parents) could be beneficial, current capabilities do not allow for such segmentation.
  • The demographic insights reveal a diverse audience aged 45 to 55 years old, indicating a need for broad appeal in messaging without specific targeting strategies.

Content Strategy and Development Frequency

Defining Content Frequency

  • The proposed content frequency includes two blogs per week, three TikTok-style videos (1-3 minutes each) weekly, and a podcast every two weeks.
  • Emphasis on the need for a specific content volume to align with web development timelines; new content should be available during the website's creation.

Content Management During Development

  • Suggestion to publish 10% to 20% of existing content while developing the website to avoid delays in progress.
  • Importance of creating a user-friendly platform that allows easy management and uploading of new content.

User Engagement and Gamification

User Interaction Features

  • Discussion about allowing users to mark videos as completed, which would trigger a points system based on their engagement.
  • Proposal for an interactive feature where completing a video prompts users with questions or surveys, rewarding them with points for correct answers.

Points System Mechanics

  • Users should have unlimited attempts at answering questions related to the video content, promoting continuous learning without restrictions.
  • Clarification that point allocation is managed by an educational team responsible for defining how many points are awarded for different types of content.

Redemption Process and Automation

Points Redemption Framework

  • Discussion on how users can redeem points through various platforms like Falabel; technical implementation needs clarity regarding automation processes.

Administrative Oversight

  • Need for an automated system that tracks point redemption without requiring manual checks from administrators; this would streamline operations significantly.
  • Suggestion that administrators receive daily updates on user activity concerning points earned, enhancing oversight without additional workload.

Discussion on Employee Engagement and Content Impact

Points System and Email Notifications

  • A hypothetical points system is proposed, where employees receive an email notification upon reaching 1000 points. This raises concerns about the volume of emails received by managers with multiple employees.

Automation and Data Management

  • The discussion shifts to the potential for automating data collection from a website into a shared drive, but it is suggested that a dedicated web dashboard would be more effective.

Dashboard Concept

  • A vision for a user-friendly dashboard is presented, allowing users to filter and download lists of employees based on specific criteria like ID numbers.

Project Scope and Impact

  • The project is described as significant due to its potential impact on employee behavior within the company, emphasizing the importance of content in facilitating this change.

Content's Role in Cultural Change

  • There’s a debate about whether content alone can drive cultural change; while it plays a crucial role, real-life experiences must align with the content for genuine transformation.

Authenticity in Corporate Culture

Connection Between Content and Reality

  • An example illustrates how engaging articles can resonate with employees but may fall flat if not supported by authentic leadership actions.

Importance of Genuine Experiences

  • Authenticity in corporate culture is highlighted; if leaders do not embody the values promoted through content, employee engagement will suffer.

Cultural Initiatives

  • The complexity of fostering collaboration among teams through various initiatives (like coaching sessions or team-building exercises) is acknowledged as essential for cultural development.

The Balance Between Content and Experience

Value of Relevant Content

  • Relevant content can inspire individuals similarly to spiritual teachings; however, disconnection between teachings and lived experiences leads to skepticism among employees.

Real-Life Application

  • Employees need to see practical applications of corporate values in their daily work life; otherwise, they may perceive initiatives as insincere or hypocritical.

Web Development Process Overview

Stages of Web Development

  • The web development process will be divided into two main stages: requirement gathering and prototyping. Each stage requires careful consideration of feedback from stakeholders.

Prototyping Phase

  • During prototyping, there will be an emphasis on creating functional prototypes that allow stakeholders to visualize how the final product will operate before coding begins.

Challenges in Collaborative Decision-Making

Managing Stakeholder Input

  • Challenges arise when multiple stakeholders provide input during development; too many opinions can hinder progress rather than facilitate it.

This structured approach captures key discussions from the transcript while providing timestamps for easy reference.

Disruptive Leadership and Team Dynamics

The Role of Disruption in Leadership

  • The speaker describes a leader as "disruptive," emphasizing clarity and approachability, suggesting that effective leadership involves challenging the status quo while remaining relatable.
  • The relationship between team members is highlighted; mutual understanding leads to shared preferences, indicating that genuine communication fosters collaboration rather than authority.

Feedback Mechanisms and Project Management

  • A focus on fluidity in processes is discussed, with an emphasis on the importance of timely feedback to avoid project stagnation.
  • The speaker critiques individuals who excessively alter projects for the sake of feeling valuable, advocating for respect towards expertise in specific areas like web usability.

Structuring Feedback Sessions

  • Proposes establishing weekly feedback meetings over a month to streamline input and ensure clarity before finalizing any project elements.
  • Acknowledges the challenge clients face in articulating their needs until they see tangible results, stressing the need for efficient timelines to prevent delays.

Domain Management and Accessibility

  • Discusses the necessity of defining where a project will reside online, mentioning intranet use for internal management versus public domains for broader access.
  • Suggests creating a secure domain requiring user login to protect sensitive information while ensuring it remains visually appealing.

Payment Structures and Incentives

  • Clarifies payment terms, proposing options such as phased payments or full payment after 30 days post-project initiation to encourage prompt financial commitment.
  • Emphasizes the importance of structuring payments to incentivize timely completion of tasks while maintaining flexibility based on client needs.

Payment Structure Discussion

Payment Terms and Project Timeline

  • Discussed the importance of payment timing in relation to project completion, suggesting an 80/20 split where 80% is paid upfront and 20% upon finalization.
  • Emphasized that companies typically do not pay before work is completed, highlighting a common industry practice.

Anticipation Payments

  • Explored different options for payment structures, including potential mid-project payments (50%) versus a more traditional model. Suggestions included variations like 60/40 or 80/20 splits.

Project Responsibilities and Content Creation

Team Involvement

  • Clarified roles within the project team, indicating that one individual would oversee the project while others handle specific tasks related to content creation.

Content Production Insights

  • The current inventory includes approximately 12 videos ready for publication, with an additional 20 in various stages of ideation. Articles are also being produced at a rapid pace, with the potential to create up to ten articles weekly.

Content Strategy and Publication Process

Proposed Content Output

  • Suggested immediate action items for quick publication: five articles and five videos to expedite the process of developing the platform for easier content management. This approach aims to streamline future publishing efforts.

Request for Examples

  • Requested examples of existing video content and articles post-meeting to better understand their format and style for future planning purposes. This will aid in aligning expectations on content quality and presentation.

Defining Project Scope

List of Topics and Subtopics

  • Highlighted the need for a clear list of topics and subtopics that will be included in the proposal to avoid scope creep during project execution; any new subtopic introduced later may fall outside initial agreements.

Flexibility in Topic Management

  • Discussed how subtopics can be managed independently by the team without needing constant oversight from leadership, allowing flexibility while still tracking student progress effectively. This autonomy is crucial for adapting over time as needs change.

Proposal Preparation

Hosting and Methodology Proposals

  • Mentioned upcoming tasks such as preparing proposals related to hosting services and publication methodologies across platforms like YouTube or other media outlets; these must be established early on to ensure smooth operations moving forward.

Timelines for Feedback

  • Stressed that timely feedback from clients significantly impacts project timelines; delays often stem from client-side responses rather than internal processes, which can affect overall delivery schedules negatively if not managed well.

Discussion on User Engagement and Platform Features

Content Uploading and User Interaction

  • The ease of uploading content and questions is emphasized, highlighting the importance of marking correct answers and tracking user attempts.
  • Discussion about whether points in the platform should expire; one participant expresses indifference towards point accumulation, indicating a lack of engagement with existing systems.

Communication of Benefits

  • There is a need to communicate the benefits associated with points on the platform, as users may not be aware of their potential uses.
  • One participant feels positive about the discussion but suggests that further inquiries or comments could enhance understanding.

Technical Considerations for Accessibility

  • Acknowledgment that most users connect via mobile devices, stressing the necessity for optimization across both mobile and desktop platforms.
  • The priority for development is mobile accessibility due to high usage rates, although initial focus may still lean towards desktop usability.

Project Development Timeline

  • Inquiry into how long the project has been in development; previous content efforts were hindered by team workload distribution.
  • Transition from Microsoft’s Engánchate to Google tools under new leadership aimed at enhancing technological integration within company culture.

Strategic Planning and Value Perception

  • Recent strategies have emerged focusing on emotional engagement through content creation, reflecting a shift in approach over recent weeks.
  • Emphasis on developing a custom-coded solution rather than using generic platforms like WordPress; this highlights an investment in quality and tailored functionality.

Importance of Clear Deliverables

  • Discussion around ensuring clear communication regarding project deliverables; perception of value must align with what is presented in quotes and contracts.
  • The significance of providing detailed prototypes to ensure mutual understanding between developers and clients regarding expectations.