Notes from Transcript

Edge of Eye Use Cases

  • Meeting to discuss edge of eye use cases.

  • Jen in Toronto is considered a genius and valuable asset.

Introductions

  • Introductions of team members, including Robert (intern).

  • Acknowledging previous meetings and attendees.

MSP Perspective

  • Need help creating a vision from the MSP perspective to sell to others.

  • Binet as a potential champion for other product lines.

  • Aim to align everyone with this perspective.

Diagram Modification

  • Modifying the SDK diagram to align with Jen's vision.

  • Using the diagram as a window to guide customers.

  • Strategy: Leverage existing strategies and align them with the diagram.

Diagram Structure

  • Keep the existing format with potential renaming of boxes.

  • Goal: Use the diagram as an introduction, with the core content residing elsewhere (e.g., dev).

  • Avoid overwhelming users with too much text; present a landscape view.

SDK Diagram Purpose

  • The diagram is a marketing message showing the SDK suits user needs.

  • Acts as a graphical user interface to SDK portions, highlighting key aspects and structure.

  • Focus on hero items for credibility, expanding on the story with links to TREC.

  • Avoid cramming everything into the diagram.

  • The diagram is a tool to help navigate TREC.

TREC Integration

  • Use the diagram to organize TREC content and clean it up.

  • Direct customers to the correct folders on TREC using appropriate language.

Editable Text

  • Concern about fixed text like "MSP SDK examples" and its impact on new middleware.

  • Consider the "and more" approach to indicate non-comprehensive content.

Middleware Landing Page

  • Possible introduction to middleware page for additional information.

  • This page can be edited to add more examples.

  • Potential for improving the UX interface for in-depth content.

TI Resource Explorer

  • Efforts to redo tagging in the middleware for projects like STAR Hub.

  • A middleware landing page would facilitate updates with new middleware.

Diagram Editability

  • Populating the diagram via AEM for easier content entry.

  • Commitment to keeping the diagram up to date with new middleware and relevant updates.

  • Determining optimal layout (e.g., number of columns and lines) for SDK sections.

Value Proposition

  • How to convey the value proposition before users click off the page.

  • Launching links in new tabs to keep the diagram visible while directing users to TREC.

  • Layered approach: overall SDK value proposition, followed by specific value propositions within each area.

  • Aim to surface 10 or fewer key examples to satisfy most customers.

TREC Destinations

  • Mapping destinations in TREC and ensuring they provide a good user experience.

  • TREC space shouldn't be overwhelming or treated as documentation.

  • The diagram serves as a graphic illustration, with Resource Explorer as the conventional documentation.

  • Making it clear to customers that the diagram is a high-level picture and they'll be directed to TREC for details.

Content Focus

  • Evaluating content choices such as MSP subsystems versus other examples.

  • MSP subsystems might not resonate as much as application-focused examples like automotive or motor control.

  • Balancing marketing for subsystems with providing relevant examples.

Rethinking the Graphic

  • Rethinking the graphic to align with the design and development vision.

  • Ensuring the graphic works and resonates with the customer journey.

Diagram Purpose

  • The graphic shouldn't replace dev or become a documentation dump.

  • It should reflect the software story and overall strategy.

MST Subsystems

  • Outline MST subsystems in the content below, but pull most examples up.

  • Balance low-level examples with category-specific value propositions.

MSP Folder Description

  • Condensing information into shorter, engaging phrases.

  • Using top-level highlights to engage customers without excessive explanation.

Dev Integration

  • Problem: Inability to link to every file in dev like in the accordion.

  • Solution: Create an intro to middleware page to guide customers.

Maintenance

  • Addressing the maintenance effort required to update the diagram with new code examples.

  • The top-level page on TREC can be maintained more easily.

Intro Page

  • Creating a landing page for middleware with improved navigation.

  • Directing people to precise folders with cleaned-up directory structures on TREC.

Directory Structure

  • The SDK directory structure needs improvement to align with high-level middleware buckets.

  • Automated tooling generates metadata for code examples.

Processor SDKs

  • Processors have a landing page that include documentation, examples.

Tags

  • Adding technology and equipment tags to code examples for better categorization.

  • Tagging every code example manually.

Strategic Organization

  • Strategically organizing content focusing on the front end.

  • Aligning tags, middleware, and diagram categories.

Visualizing Content

  • Putting content in the Figma framework for visualization.

  • Evaluate the consequence of adding more columns to the visual framework.

UX Considerations

  • Understanding how the arrows or chevrons perform UX-wise.

  • User testing indicates intuitive use of the arrows to open content.

Content Resonancy

  • Ensuring every item in each category resonates with customer needs.

  • Aiming for a static presentation where the whole picture is visible.

Journey

  • Reworking content in the context of the customer journey.

  • Scheduling meetings to work on the content and provide feedback.

MSD Champion

  • MSD to champion the content for easier communication across business lines.