Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 13 Next »

Overview:


Quantitative Data:

Data driven justification for ux/ui changes, especially necessary for organic changes that do not originate from client requests or roadmap features.

Link

Date Range

Item

Metric & Value

Assumption

00/00/2021
to
00/00/2021
(0 Days)

Metric name

  • Metric Value

HYPOTHESES

  • Lorum ipsum

REASONING

  • Lorum ipsum


Competitor Research:

Function

Findings

Image

Takeaways

EMBRACE

REJECT

TO DISCUSS


Proposal Feedback:

Stakeholder

Date

Changes

Client - SWZD

12/05/22

FEEDBACK

  • Setup for campaign level most of the time

  • Bands level setup also required

Product

17/05/22

DONE

  • Potential scenarios are campaign and publisher level, with bands for both

  • Change from panel view to table view so it’s more of a compact interface

  • Management screen on global level similar to batch management

REJECTED

NEED MORE INFO

TO DISCUSS

TO DO

Client - Intentsify

10/06/22

FEEDBACK

  • Setup for campaign level most of the time

  • Bands level setup also required

  • Somewhere to input ‘stale’ lead timeframe? E.g. if schduled is weekly cadence, but publisher delivers all cap on 1st day of every week, setting to say that ‘this lead was invalidated because it’s over 5 days old'?

Product

14/06/22

DONE

  • Campaign information dropdown to include new section with ‘scheduled delivery’ with toggle to turn on and off

  • Any users who have access to leads table with ‘processr status’ column will have ‘on hold’ tooltip updated to account for scheduled delivery (not just mentioning batch)

  • Campaign admin screenshots was showing new platform, change to old platform as new admin section will not be released any time soon

  • New dialog to show pending and sent deliveries

REJECTED

  • ‘Stale’ lead timeframe stuff to be part of v2

  • For scheduled delivery setup, if ‘monthly’ is chosen, we need to say that if 31st day is chosen in start date, then for months with 30 days, it will default to the last day (same for leap year)

NEED MORE INFO

TO DISCUSS

TO DO

Product

16/06/22

DONE

  • Line added on the ‘View schedule’ dialog to say when the next schedule is.

  • Changing interface to have more specific options for weekly and monthly so we don’t need to have a warning about defaulting months with 31 days/leap years

REJECTED

NEED MORE INFO

TO DISCUSS

TO DO

Product

23/06/22

DONE

  • Month dropdown additional options added for ‘last business day of the month’ and ‘first business day of the month'

  • Change wording of ‘Pending/Sent Deliveries’ dialog tabs to ‘Pending/Sent Schedules’

  • Management screen > table listing > new column with ‘Next Schedule’ which lists all pubs and their next schedule

  • ‘Next schedule’ column added to table on campaign and global level (originally it was in the ‘view’ dialog)

  • Tooltip for ‘next schedule' column added to say that if scheduled for specific time may not be exact because of processing/setup complexity

    • ‘Leads will begin integration at specified time, however the exact release time can vary depending on complexity of integration and processing setup.’

REJECTED

NEED MORE INFO

TO DISCUSS

  • Scenarios that are based on specific days within a month e.g. last thursday of the month, do we need to do this?

    • Current idea is to work this out buy having a dynamic option in the ‘repeat on’ dropdown for month which updates depending on the chosen ‘start date’

      • E.g. if you select start date of ‘XXXX-XX-06’ then repeat every month on the 6th day of the month

  • ‘Days’ option maybe can be removed because all scenarios that would be required for ‘days’ can be covered by setting ‘repeat every 1 week’

    • Use case would be for when users want to not include weekend days

    • OR, ‘Days' could become a calendar dropdown where you select any amount of days within the campaign start and end time period

TO DO


Retrospective:

To be completed after this features release. The retrospective should allow a basis for further improvements to this feature.

User Feedback

Stakeholder

Date

Description

Quantitative Data

Link

Date Range

Item

Metric & Value

Assumption

00/00/2021
to
00/00/2021
(0 Days)

Metric name

  • Metric Value

HYPOTHESES

  • Lorum ipsum

REASONING

  • Lorum ipsum

  • No labels