Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Predecessor Status for Projects within ProgramsNew

Within projects, functionality exists to make tasks and subtasks dependent on completion of other tasks. This allows projects to move forward in the optimal order and timeframe. What about allowing the same type of dependencies to exist for Programs?As a project manager, I often work on multiple projects within an overarching Program (which itself exists within a Portfolio.) There may be multiple projects within a portfolio which depend on one another in order to move forward.  Currently, there is no logical connector between the health or completion of a project and starting another project. Example Program:  Spring Campaign.  Below are examples of projects which might exist within the Program.  These are not in order, but there IS an order to them. Project: Campaign StrategyProject: Content StrategyProject: Approved Marketing CopyProject: PhotoshootProject: Video ShootProject: Social AdsProject: Web BannersProject: Campaign Web PagesProject: Pitch DeckProject: Sales Enablement MaterialsProject: Partner VersioningProject: Localization Across Regions Creating functionality which allows dependencies between Projects in a Program has the potential to elevate the interconnected nature of all of the work required to accomplish a project to a level which allows visualization across stakeholders. The visualization could be a game changer in articulation of what is possible given resources, budget, and timeline to accomplish a large multi-faceted goal. The implications for conveying reality to Executive Level Stakeholders allows the vision to be seen in the light of reality. Accountability is underscored by the clear understanding of ALL that is involved.  Silos are removed.

Caveman77Level 4

Ability to create an audience and include audience who have receive a specific Journey Name or Message Naming structureInvestigating

Description:We use a specific naming structure for our Journeys and our message names.  We want to be able to Query this Name when creating an audience, instead of having to use Journey ID or Message ID.   Why is this feature important to you:As I empower more teams to work on campaigns as standalone teams, including test variations with split tests, I need to have overarching criteria that will allow me to all audiences who have received a type/class of mailing without having to create a manual list of Journey ID or message IDs   How would you like the feature to work:For instance, if all emails with an Offer use "-OFFER-" in the message name, then I want to be able to create and audience with anyone who has received a message with "-OFFER-" in last X months and not have to recall all the journey IDs.  Similarly, if a customer has been in any journey that begins with "XYZ-" in last X day I want may want to exclude them. I don't want to have to search all possible Journey IDs.  This becomes impractical to scale up. Alternative option:  Let me tag every journey or message and use those tags for audience segmentation.  (Preference would be for Journey or message names over tags) Current Behaviour:Can only use MessageID or JourneyID.  Have to ask all teams to remember and add these to a centralized audience - this will have issues based on human error.