AMA: Josh Brewer & Tim Van Damme - Abstract

almost 5 years ago from Tim Van Damme, Designer at Abstract

  • Tim Van DammeTim Van Damme, almost 5 years ago
    1. Absolutely! The design process is a combination of people, team size, product type, market... Meaning that it's very different at every single company. Team members bring in tricks they learned at previous gigs, and the combination of all this is a process that will probably be different next month.
    2. Abstract is made for everyone who's even remotely involved in the design process. Designers (obviously), design managers, project managers, engineers, VP's, CEO's... Whoever wants to take a look at the work that's been done by the design team, can do so with Abstract.
    0 points
    • Niels MulderNiels Mulder, almost 5 years ago (edited almost 5 years ago )

      Thanks.

      I often work with JIRA to keep track of open issues and to do's. Also a lot of engineers use these kind of tools to manage their work process. And tools like Zeppelin luckily help us document less and less in environments like Confluence.

      Where does Abstract fits in this field?

      0 points
      • Tim Van DammeTim Van Damme, almost 5 years ago

        It fits however you want it to fit. Personally, we use Github Issues to keep track of our to do's, and I'll typically create a new branch in Abstract per issue. There are some nice parallels which keep coming back. Over time we'll learn more and see which other parts we can focus on.

        0 points
      • Josh BrewerJosh Brewer, almost 5 years ago

        We're planning to do integrations with products like JIRA, Github, etc so that we can help keep these things in sync. Abstract is the reliable record of all the work—ongoing and completed—allowing the design team, PMs, Engineers, Marketing, etc all to have one place to reference, leave feedback, and track the work.

        2 points
        • Jonathan SimcoeJonathan Simcoe, almost 5 years ago

          What would GitHub sync look like? Would it allow us to keep approved versions of .sketch assets in a GitHub repo? This would allow integration with out Git and npm tools we use to build UI from Sketch files.

          0 points
          • Josh BrewerJosh Brewer, almost 5 years ago

            We are just starting to think about that so I don't have a concrete answer for you just yet. But yes, generally, that would be something we would like to see happen.

            0 points
    • Matt Bond, almost 5 years ago

      It's cool if a VP can jump into see that work in progress but I sure as hell don't want someone that high up asking why something is 16px and not 20px -- I want to tell them a story about/present the work. Will abstract help with the storytelling side of design?

      0 points
      • Tim Van DammeTim Van Damme, almost 5 years ago

        Absolutely! In a couple of different ways even:

        1. Commits: Every time a designer creates a commit, we ask them to basically document why they made changes while we take care of the "what." This creates a rich history of how a design came to be, including comments made by other people inside the org.
        2. Merge history: The above history trail is easy to pick up across different branches, whether they're archived or merged.
        3. We're working on a pull request with a twist which will include some other mechanics of creating a story around what you're working on.
        0 points
      • Josh BrewerJosh Brewer, almost 5 years ago (edited almost 5 years ago )

        +1 to everything that Tim said. And if a VP is paying close enough attention to the design system that they can spot something out of whack, why are you afraid of that? Wouldn't you rather have anyone (including a VP) catch that before it goes out?

        0 points
        • Matt Bond, almost 5 years ago

          I think you've misunderstood -- I was referring to the case where higher ups ask clarifying questions, not pointing out that something is wrong.

          And if a VP is paying close enough attention to the design system that they can spot something out of whack, why are you afraid of that?

          Sweating those details, while it might seem like they truly care about design, is not something I want a VP doing. Trust your team, go back to doing VP things.

          Wouldn't you rather have anyone (including a VP) catch that before it goes out?

          Product teams I've worked on ship software, not Sketch files.

          1 point