Cover image for an AI-driven Content Creation Hub

UX Design for an AI-driven Content Creation Hub

UX UI DESIGN

Role

UX UI Designer

Team

Product Owner, Engineers, UX Designer

Duration

1 month

Being a web development company, my client is well aware of the time and costs that small businesses encounter when creating content for their websites.

Our main goal was to craft a tool specifically for Small and Medium-sized Businesses (SMBs), allowing them to generate engaging content while incorporating AI technologies to reference previously captured information about their company, adding value to the product.

This project was a collaborative effort with a team spanning across South Africa, India and the US. While leading the product design, I maintained constant communication with the team.


Discovery + Planning

I led remote sessions for stakeholder interviews and collaborative workshops to elicit and refine project requirements.

Following remote discovery interviews with the Product Owner, we discerned that our user base would be diverse, but our primary focus would be on SMB owners requiring a cost-effective tool for marketing content creation. To align our efforts, I delved into understanding the business goals in order to formulate a pertinent strategy plan.

Quotation marks
Create an app for SMBs to produce cost-effective, compelling content.

Key business goals

Create a new revenue stream

Leverage expert knowledge of AI prompt creation

Offer a competitively priced service

Use as an internal tool for content creation

System and Technical Requirements

The project had its roots in an initial idea that required thorough exploration for proper definition. I engaged in extensive research on various products, leading to collaborative efforts with the team to precisely articulate our project goals over time.


UX Reseach

Competitor Research

My research kicked off by exploring AI-driven content creation tools like Speechform and Grammarly. Given the dual role of our project as an editor/creator and file storage, akin to the functionalities of Dropbox and Google Drive, I delved into CMS platforms such as CMS Hub, WordPress, Shopify, and others.

I then pinpointed potential competitors like ClickUp, Narrato, Jasper, and Copy.ai, all emphasizing the fusion of content creation and CMS functionality while leveraging AI.

Screenshot of researching Grammarly
Screenshot of researching Google Drive

With this knowledge we could begin defining the product as a team.

Gathering this information enabled me to envision the positioning of our product within the competitive landscape. It also provided valuable insights into prevalent and effective UX concepts employed by other products. This knowledge is instrumental in crafting a design that is not only user-friendly but also familiar to our users, facilitating ease of learning and use.

Screenshot of researching Narrato

SYNTHESIZE + DEFINE

Based on our findings, I created proto personas, outlined problem statements, and developed user stories.

Quoatation marks

I'm striving for impactful results without draining my limited resources.

User pains + needs

My content is scattered across various platforms

Challenging to craft effective marketing content

Struggle to maintain a consistent tone

I'd like to reuse previously created content

I'm already overwhelmed with my workload

Screenshot of user research for the product

UX DESIGN

I started by structuring the system for a clear and user-friendly information flow, focusing on logical taxonomy and user mental models.

Our first step was to determine the core system functionality, and I facilitated this process by developing system architecture diagrams. These visual aids helped us confirm or eliminate concepts, features, and roles.

After reaching a consensus on the system functionality, I proceeded to analyze user journeys to ensure coherence in the sitemap and clarity in naming conventions.

Types of questions we needed to figure out as a team:

—   What mental model will our users have when signing in for the first time?

—   Do we use a 'folder' structure, like Google Drive or create something new?

—   What folder and storage naming conventions make sense?

Image displaying the system functionality diagram
Screenshot of researching Adobe Express taxonomy
Image displaying the a sitemap idea

System functionality; referencing apps (like Adobe Express) for ideas on taxonomy and microcopy; sitemap formulation

Wireframes + Walkthroughs

Armed with insights into the system's structure and core functionality, I embarked on sketching ideas for the layout and user experience. These initial sketches were intentionally rough, allowing us to swiftly discard any undesirable concepts and explore fresh ones.

Sketched wireframes for each main section
Sketches ideating different interactions for the user experience

Testing out different type of site layouts, interactions and animations which would best suit our product and user needs, and match our tech stack.

We tested concepts with paper and lo-fi interactive prototypes.

In this phase, we leveraged user stories to test prototypes, ensuring that users could seamlessly execute essential tasks as outlined. Additionally, we engaged in brainstorming sessions to explore various naming conventions and strived to establish a cohesive and consistent tone for the product.

Sketched wireframes for the steps invloved in creating new content
Sketched wireframe for the dashboard
Closeup of sketch for editor

Once the design concept was finalized, I swiftly developed a low-fidelity interactive prototype. This allowed for a systematic evaluation of each system section, ensuring alignment with user requirements and Product Owner expectations. Developers actively participated in the process, providing valuable feedback during demo reviews.

A collection of the lo-fi wireframes that were created

VISUAL AND UI DESIGN

I opted for a strategic design approach utilizing minimalism and rapid prototyping.

Given time constraints, I swiftly introduced essential concepts and converted low-fidelity designs into functional prototypes. Despite a tight deadline and the absence of precise branding guidelines, I opted for a clean and minimalist aesthetic, avoiding any superfluous design elements.

Product screenshot for the user dashboard

1. Select the content type you wish to create

Crafting a new article has never been simpler. Alternatively, opt for pre-set templates designed to streamline the process and save you valuable time.

Product screenshot for creating a new document

2. Provide the AI Helper with key details about your chosen topic

Simply input the topic or offer a brief description, allowing the AI Helper to initiate the laborious research and content creation on your behalf.

Product screenshot selecting information references

3. Utilize information stored in your reference library

Let the AI sift through your content library to identify relevant information that can enhance your article.

Product screenshot for selecting text to rewrite

4. Edit and customize your generated content in the editor

This is where the magic unfolds. Add your preferred tones, perspectives, or insert personal insights to tailor the content to your liking.

Product screenshot for clicking through various rewrite options

5. Easily update and refine selected content

Harness the power of the AI Helper to effortlessly rephrase and update your copy with a single click, facilitating quick and effective revisions to your copy.

Smooth design handover for efficient development

Developers received XD prototypes with detailed design specifications, a reusable component library, and elements ready for export. Clear user flows, based on user stories, guided developers through essential tasks, ensuring a smooth user journey. Additionally, comments within XD clarified animations and key interactions.


TAKEAWAY

Transforming a vision into reality

My involvement in this project concluded after handing it over to the developers. However, I remain optimistic that it will be intuitive, ensuring a pleasant content creation experience.

One significant lesson from this project emphasized the value of mental models. We dedicated considerable time to brainstorming naming conventions that resonated with our users.