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 14 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

Product

17/03/23

DONE

  • ‘Connect’ sidebar item

    • This should show even if credential manager hasn’t been configured

    • If users navigate to ‘connect’ in sidebar without credential setup, the listing will be empty

  • Campaign processr < visibility for publishers

    • For v1 this should be asingle toggle to apply to all publishers

    • V2 may have ‘per publisher selection’ if required

  • Tab terminology

    • Changed from ‘Active Configurations’ and ‘Inactive Configurations' to ‘Pending Configurations’ and ‘Complete Configurations'

  • Campaign selection (setup step)

    • Select ‘existing campaign’ should have advertiser filter first

    • Configration applying should be a 1 to 1 relationship, therefore the interface needs to change because you should only be able to select 1 campaign to apply the configuration to so no need for the ‘associated campaigns’ column on the listing. Users can then duplicate the campaign if they want to separate their lead delivery into multiple campaigns.

  • Dashboard

    • New column to show if campaign is ‘connected’

  • ‘Connect’ listing

    • Needs ‘domain’ column and ‘advertiser’ column

REJECTED

  • Potentially merge management screen with ‘dashboard’ somehow, maybe new tab?

    • Instead, have indicator on dashboard that campaign is ‘connected’

NEED MORE INFO

TO DISCUSS

  • Multiple ‘connect’ campaigns scenario

    • If a campaign with a configuration applied is duplicated, will it also be ‘linked’ to the recieving leads enterprise and receive leads?

  • Changing the campaign to apply the configuration to

    • In the ‘configure’ dialog, the chosen campaign can be changed?

    • Or once it’s applied, then it cannot be changed and the link between the campaign and the configuration is permenant?

      • If this is the case, what happens if a customer accidentally chooses the wrong campaign to apply it to? Because the campaign link is permanent, they can’t change the campaign?

  • Handing of updates

    • If a configuration change is made on recieving leads enterprise (i.e. a job is updated, job is added, job is removed) how do we track and send this across enterprises? Via job id?

  • In mappings, currently can only reference fields in processr once a lead is in because the fields come from the lead data

    • Can we change behaviour so fields come from associated form on the campaign? Therefore a lead does not have to be submitted before fields can be referenced in any mappings.

TO DO

  • ‘Configure’ step 2, for ‘validation lists’ values will not be shown in column because there could be too many to show

    • But if we have ‘view details’ then it could have table with pagniation of values

  • Step order changes

    • 1 is setup, 2 is form (which has mapping stuff)

    • Mapping is required on ‘form’ not on ‘job’

    • If select from linked enterprise then mapping is ‘done’ because sending enterprise has already done the mapping

    • If select own form, then mapping is required to map ‘local’ form fields to ‘linked enterprise’ form fields

  • Configuration pending updates

    • On jobs step, have column for ‘type of update’ then highlight the jobs that have been added, changed, removed (tracked based on campaign ID)

  • Audit of changes

    • Details will be on system level

  • Campaign level connect integration

    • The ‘connect’ integration will be added, but without bits like API key and domain and this is done via credential manager

  • Domain column added

    • This means that users can add credentials for multiple enterprises and have campaigns from multiple sources come in, is there an existing customer that does this right now?

  • Mapping fields for QA jobs

    • If user selects ‘local’ form, map these fields to ‘linked enterprise’ fields

    • Option to select ‘none’ if mapping is to be done later


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